Skip to main content
This page covers the shared pieces every GetWhys MCP connection uses. When you’re ready to connect a specific app, pick it from MCP Overview or the sidebar.

​
Before you start

You’ll need:
  • An MCP-compatible app — sometimes called an MCP client or host. This is whatever assistant or tool you want GetWhys to plug into.
  • A GetWhys account for an individual connection, or GetWhys admin access for a shared organization connection or API token.
  • The GetWhys MCP endpoint: https://api.getwhys.io/mcp/org.

​
The GetWhys MCP endpoint

GetWhys runs a hosted (remote) MCP server, so you don’t need to install anything. Use this URL for all new connections:
Connection type: remote URL over HTTPS. Use /mcp/org for all new connections.

​
Choose your authentication method

Use an OAuth MCP Connector when one centrally managed connection should provide organization-level access. Prefer this method when your MCP client accepts a client ID and secret.
  1. Go to app.getwhys.io/settings/integrations.
  2. Under OAuth MCP Connector, add a label and click Generate.
  3. Copy the Connector URL, OAuth Client ID, and OAuth Client Secret. The secret is shown only once.
  4. If your MCP client provides redirect URIs, click Edit URIs and add them to the connector.
  5. Enter the connector URL and OAuth credentials in your MCP client’s organization-level OAuth settings.
When the client connects with the registered client ID and secret, GetWhys authorizes organization-level access. Teammates do not sign in to GetWhys individually for that connection. If your client requires the OAuth endpoints or discovery documents explicitly, use:

​
Individual OAuth

Use individual OAuth when each person should connect their own GetWhys account. Enter https://api.getwhys.io/mcp/org without a client ID or secret. A compatible MCP client discovers the GetWhys OAuth configuration and uses Dynamic Client Registration (DCR) to register itself. The client then sends you to GetWhys to sign in and approve access. The resulting connection is tied to your GetWhys user. Your MCP client manages the OAuth credential for you.
Use an API token only when your MCP client cannot use OAuth with a client ID and secret or individual OAuth.
  1. Go to app.getwhys.io/settings/integrations.
  2. Open the API tokens tab under MCP.
  3. Add a label and click Generate.
  4. Copy the token immediately. GetWhys shows it only once.
  5. Configure your client with the MCP endpoint and authorization header below.
Use a distinct label for each client so you can revoke one connection without affecting the others. Do not put an access token in the server URL.
GetWhys also supports Enterprise-Managed Authorization (EMA) for compatible identity providers. The client guides do not recommend this path yet because GetWhys has not validated it end to end with an LLM client. Contact [email protected] if you want to evaluate EMA.

​
Org-wide setup is per surface

Organization credentials provide shared access, but you still configure GetWhys separately on each surface where you want it available. Setting it up in one place does not automatically enable it everywhere.
Claude.ai does not set up Claude Tag. Even if GetWhys is already available as a connector in Claude.ai, you still need to complete Claude Tag separately — Access bundles, credentials, and plugins for Slack are provisioned on their own.Claude Tag is also not the GetWhys Slack bot. The Slack bot is a separate GetWhys integration; Claude Tag brings GetWhys into Anthropic’s @Claude in Slack.

​
Next: pick your client

Claude.ai / Desktop

Organization connector and the GetWhys skill.

Claude Code

Local CLI setup with individual or organization OAuth.

Claude Tag (Slack)

Access bundles and plugins for @Claude in Slack.

ChatGPT

Developer Mode connectors in ChatGPT.

Gemini Enterprise

Custom MCP Server data store in Google Cloud.

Microsoft 365 Copilot

Federated connector for Microsoft 365 Copilot Chat.

Writer

WRITER Agent via Writer’s MCP gateway.

Typeface

Typeface MCP via OAuth.

Generic MCP client

Cursor, custom agents, or any other MCP-compatible app.

​
Verify the connection

Once connected, confirm it’s working by asking your assistant:
“Who am I in GetWhys?” — or — “Check my GetWhys connection.”
This runs the whoami tool. Individual OAuth returns your user and organization. An OAuth MCP Connector or MCP API token returns organization-level context.

​
Authentication & permissions

Individual OAuth uses your existing GetWhys account and permissions. An OAuth MCP Connector and MCP API token use organization-level access without representing an individual user.

​
Security, data access, & privacy

All data transmitted through GetWhys MCP is encrypted in transit and at rest. Your MCP client handles individual OAuth credentials. Keep client secrets and API tokens private. Enter them only in the intended platform’s secure connector settings, and never commit them to source control. Data shared via MCP is governed by your organization’s existing data protection agreement with GetWhys.

​
Revoking access

For individual OAuth, disconnect GetWhys from the MCP client. For organization OAuth, return to Integrations, find the connector under OAuth MCP Connector, and click Revoke. For an API token, open the API tokens tab and click Revoke next to the token. Revocation takes effect immediately.

​
Pricing & support

GetWhys charges a flat rate for unlimited MCP access. If GetWhys MCP isn’t yet enabled for your organization, contact your workspace owner or your GetWhys contact. For support, reach out via Teams, Slack, Google Chat, or email [email protected].