Generic MCP client

Use this guide for Cursor, a custom agent, or any other remote MCP client that doesn’t have its own setup guide.

​

Connect an organization (recommended)

Use this method when the client accepts an OAuth client ID and secret. The connection has organization-level access and isn’t tied to one GetWhys user.

1. Generate an OAuth MCP Connector in GetWhys. Copy the OAuth Client ID and OAuth Client Secret.
2. In your MCP client, add a remote HTTP server with the URL https://api.getwhys.io/mcp/org.
3. Choose OAuth with a pre-registered, user-defined, or custom client. Enter the GetWhys client ID, client secret, and mcp:tools scope.
4. If the client displays a redirect or callback URI, add it to the GetWhys connector under Edit URIs.
5. Complete the connection flow.

OAuth discovery and endpoint values

Compatible clients should discover these values automatically from the MCP server URL. If your client asks for metadata or endpoints, use:

Field	Value
Protected resource metadata	https://api.getwhys.io/.well-known/oauth-protected-resource/mcp/org
Authorization server metadata	https://api.getwhys.io/.well-known/oauth-authorization-server/mcp/org
Authorization URL	https://api.getwhys.io/mcp/org/oauth/authorize
Token URL	https://api.getwhys.io/mcp/org/oauth/token
Scope	mcp:tools
Token endpoint auth method	client_secret_basic
PKCE method	S256

​

Connect an individual account

Use this method when the connection should use your GetWhys user and permissions.

1. Open your app’s settings and find the section for integrations, connectors, or MCP servers.
2. Add https://api.getwhys.io/mcp/org as a remote HTTP server and choose OAuth.
3. Leave the client ID and client secret blank.
4. Sign in to GetWhys and approve the connection when prompted.

GetWhys uses OAuth discovery and Dynamic Client Registration (DCR) to register compatible clients automatically.

​

Verify the connection

Ask your assistant: “Who am I in GetWhys?” An individual connection returns your user and organization. An organization connection returns organization-level context.

​

Troubleshooting

The OAuth callback fails — copy the client’s redirect URI exactly and add it to the GetWhys connector under Edit URIs. The client asks for authorization details — use the discovery and endpoint values above. The client supports only local command-based servers — it cannot connect directly to the hosted GetWhys endpoint. Use a client that supports remote HTTP MCP servers.