Skip to main content
Zudo exposes a remote MCP server so AI apps can use the same machine-facing capabilities as the Zudo API.

​
Connection details

  • Server URL: https://zudo.so/mcp
  • Auth: OAuth with authorization code + PKCE
  • Recommended scopes: mcp api
If you self-host Zudo or use a staging environment, replace https://zudo.so with your own origin.

​
What the MCP server can do

The MCP tool set mirrors Zudo’s external API — every API operation is exposed as a tool, so the two never drift apart: Some things stay out of MCP on purpose:
  • Organization settings, members and billing, and integration and connection configuration — console concerns, and exposing them would widen the blast radius of an OAuth grant without making an agent more useful.
  • Issue fields that mirror the upstream tracker. Linear owns an issue’s state, title and description, so a write here would be overwritten on the next sync. Linking an issue to a request is available.
  • Traits owned elsewhere. Only user-defined traits can be written. Zudo traits are what Zudo works out itself, platform traits are overwritten by their connection’s next sync, product traits arrive with events, and smart traits are computed from a formula — list_traits marks each one writable so a client can tell which is which. list_account_traits returns an account’s Zudo traits, such as its renewal date and last active date, alongside the rest.
  • Generating AI artifacts. Summaries, pulses and prep can be read over MCP but not generated, so an AI client cannot run up model spend. Generate them in the app.
  • Segment and indicator definitions, which are authored in the app where the condition builder and the trait vocabulary live.
The full reference, including every parameter, is at zudo.so/api/v1/docs.

​
How authentication works

1

Add the MCP server in your AI app

Enter the Zudo MCP server URL: https://zudo.so/mcp.
2

Sign in to Zudo

If you are not already signed in, Zudo redirects you to the normal sign-in flow and then returns you to the OAuth approval page.
3

Approve access

Zudo shows a consent screen listing the client name, redirect URI, and requested scopes.
4

Let the client store the tokens

The AI app receives an OAuth access token and refresh token. You usually do not need to copy or manage these manually.

​
Organization scoping

Your MCP connection is bound to the same organization scope as the API key record behind the OAuth grant.
If you belong to multiple organizations, switch to the correct organization in Zudo before approving the connection.

​
When to use API keys instead

Use an API key when you are building direct REST API integrations or running backend jobs against /api/v1. Use MCP when you want an AI client to discover tools and call Zudo through the MCP protocol.

​
Advanced connection info

Most clients can discover everything automatically from the MCP server URL. If a client asks for explicit OAuth metadata, use:
  • Authorization server metadata: https://zudo.so/.well-known/oauth-authorization-server
  • Protected resource metadata: https://zudo.so/.well-known/oauth-protected-resource/mcp
  • Authorization endpoint: https://zudo.so/authorize
  • Token endpoint: https://zudo.so/token

​
Troubleshooting

  • If the client connects but tool calls fail, make sure the granted scopes include api as well as mcp.
  • If you hit a sign-in loop, sign out of Zudo in your browser and restart the connection flow.
  • If data appears to come from the wrong workspace, switch organizations in Zudo and reconnect.
  • If your client supports removing or resetting a connector, disconnect and reconnect to force a fresh OAuth grant.

​
App-specific guides