Skip to main content
Use https://api.muveya.com/mcp as the Streamable HTTP server URL in an MCP client that supports OAuth authorization. You do not need an API key for MCP. API keys continue to authenticate the separate /v1 API.

​
Connect

  1. Add the server URL to your MCP client and choose its OAuth sign-in option.
  2. The client discovers Muveya’s authorization server and opens a browser. If you are signed out, Muveya Console asks you to sign in first.
  3. Choose the dental clinic whose data you want the client to access. Review the application’s name and requested permissions on Authorize an MCP connection.
  4. Select Authorize to grant the displayed access, or Deny to cancel. The browser returns to the MCP client. The client then sends its access token automatically.
The connection can only use the permissions granted to both the application and your current clinic membership. Removing your membership or revoking the application’s access stops subsequent calls. Each connection is limited to one dental clinic.

​
Available permissions

clinics:read and fulfillment:read are also supported scopes, although no current MCP tool requires them. The three person-specific tools that require approvals.decide or fulfillment.pick remain unavailable over this read-only OAuth connection. See MCP tools.

​
If connection fails

For a custom client, follow OAuth 2.1 authorization code with PKCE and Muveya’s protected resource metadata. The client obtains and stores the access token. Do not paste a token into a chat or a shared configuration file.