Skip to main content
Reyda’s guided setup covers ChatGPT and Claude. You can use another MCP client, such as Cursor, VS Code or a tool you build yourself, once Reyda has registered it. This page explains what the client needs and how to get it registered.

​
Why registration is needed

Reyda only accepts AI clients it has registered in advance, each with its own client ID and exact callback URLs. It doesn’t support automatic (dynamic) client registration, and it doesn’t accept wildcard callbacks. This keeps every connection tied to a client Reyda knows about.

​
What the client must support

Clients that need a client secret are supported: an administrator configures the secret in the client, and Reyda never shows it in the setup guide.

​
Get your client registered

1

Find your client's callback URL

Check your client’s settings or documentation for the exact OAuth callback (redirect) URL it uses.
2

Ask Reyda for a client ID

Email support@reyda.ai with the client you want to use, its callback URL, and whether it uses a client secret. Ask for a client ID.
3

Configure the client

Enter the server URL and the client ID Reyda gives you. If the client asks for scopes, request the read scopes: opportunities:read, documents:read, pipeline:read and intelligence:read.
4

Connect and approve in Reyda

The client sends you to Reyda. Sign in, review Connect your AI assistant, and click Allow read access.
5

Check the connection

Connections from registered clients appear on the AI assistants tab of Settings → Integrations under the client’s name. A good first call is reyda_get_context, which describes the connection and needs no scope.
Reyda’s server publishes its OAuth details at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource/mcp on the server origin. Most clients read these automatically once you give them the server URL. See the Tool reference for endpoints, limits and error codes.
Never paste your Reyda password or a dashboard token into a client’s settings. You only sign in to Reyda on Reyda’s own page.

​
FAQ

Only after Reyda has registered the client. Without a registered client ID and an exactly matching callback, Reyda refuses the sign-in.
No. All the tools are read-only. None of them creates pursuits, edits data, starts document extraction or starts paid analysis.
Refresh tokens rotate on every refresh and expire if unused. If the client refreshes twice in parallel or reuses an old token, Reyda revokes the connection and you need to connect again.

Tool reference

Reyda MCP server

Manage and revoke connections

Limits

Last modified on October 20, 2026