> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getwhys.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Generic MCP client

> Connect GetWhys to Cursor, custom agents, or any other MCP-compatible app not covered by a named client guide.

For Cursor, or any other MCP-compatible app not covered by a named client guide. Complete the shared steps in [MCP Setup](/integrations/mcp-setup) first (endpoint, auth method, and — for org-wide setup — an [Organization MCP API Token](/integrations/mcp-setup#generate-an-organization-mcp-api-token)).

## Recommended: org-wide via token

In your app's organization-level settings, under integrations / connectors / MCP servers, add:

* **Server URL:** `https://api.getwhys.io/mcp` for an Organization MCP API Token or individual OAuth; `https://api.getwhys.io/mcp/org` for an [OAuth MCP Connector](/integrations/mcp-setup#set-up-an-oauth-mcp-connector)
* **Auth:** `Authorization: Bearer <your-token>` header for org tokens (preferred — see [header vs. query string](/integrations/mcp-setup#authenticating-with-a-token-header-vs-query-string) if your app doesn't support custom headers)

## Alternative: individual account (OAuth)

Best for one person testing on their own account. This setup applies to **your account only** — it won't enable GetWhys MCP for anyone else in your organization.

1. Open your app's settings and find the section for integrations, connectors, or MCP servers.
2. Choose **Add** (e.g. "Add integration," "Add connector," or "Add MCP server").
3. Paste in the GetWhys MCP address: `https://api.getwhys.io/mcp`
4. The app will send you to GetWhys to authorize via OAuth. Sign in with your GetWhys account and approve the connection.
5. You'll see GetWhys listed as a connected/active integration.

## Verify

Ask your assistant the [verify prompt](/integrations/mcp-setup#verify-the-connection): "Who am I in GetWhys?"