Developers

Umovi integration platform

Test MCP

Connect an MCP client, inspect descriptors and verify account-linked flows.

MCP Inspector

Run the official Inspector against a local or public gateway:

npx @modelcontextprotocol/inspector@latest \
  --server-url https://u-agent.m-cloud.pl/mcp \
  --transport http

Verify initialize, tools/list, public discovery and the OAuth challenge returned by a protected tool.

ChatGPT or another hosted client

Add this server URL in the client's MCP/connector settings:

https://u-agent.m-cloud.pl/mcp

Refresh the connection after tool descriptors change. Test these flows separately:

  1. Search for a place without linking an account.
  2. Ask for availability without a date and verify the next seven days are searched.
  3. Link an Umovi account and list upcoming bookings.
  4. Create a first booking that requires the provider data-sharing acknowledgement; verify the client shows the notice, waits for the person's active acknowledgement and sends providerDataDisclosureAcknowledged=true only then.
  5. Reschedule and cancel only after the user's intent is clear.
  6. Read and send a message tied to an existing booking.
  7. Save and remove a place with the corresponding scopes.

Descriptor smoke request

MCP uses JSON-RPC over Streamable HTTP. A minimal descriptor call is:

curl https://u-agent.m-cloud.pl/mcp \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Do not call booking tools with hand-written bearer tokens in shared test environments. Complete the normal OAuth connection so audience, resource indicator and scopes match the MCP server.