Home / Docs / Connect

Connect an MCP client

The MCP server is at https://api.whichsitesuse.com/mcp. It uses the Streamable HTTP transport, is stateless and takes POST requests. Every MCP call needs you signed in, either through OAuth or with an API key; without one the server answers 401 and points the client at its OAuth metadata, which is how Claude and ChatGPT know to show you a sign-in.

How signing in works

When a client connects, it registers itself with WhichSitesUse and opens our consent page in your browser. If you're not signed in yet, you sign in or sign up by emailed link first, and the link brings you back to the consent page. The consent page names the app, says it can search and spend credits from your balance but can't see your payment details or buy credits by itself, and lets you set a monthly credit cap for that app. Approve it and you're sent back to the app.

Each approved app shows up on your account page as a connected app, with its usage and cap, and a disconnect button that cuts it off straight away. The app's access token lasts an hour and it renews itself with a refresh token for up to 90 days, so you won't be asked to sign in again unless you disconnect it or it goes 90 days without renewing.

Claude (claude.ai and Claude Desktop)

Go to Customize, then Connectors, choose Add and then Add custom connector. Name it WhichSitesUse, enter https://api.whichsitesuse.com/mcp as the server URL and click Continue. Keep the sign-in option Claude detects. If the dialog asks how Claude identifies itself under OAuth client, choose Register automatically, because WhichSitesUse supports dynamic client registration but not Claude's published identity. Click Add, then Connect, and approve the connection on our consent page. On a Free plan this uses your one custom connector.

On Team and Enterprise plans, an Owner adds the connector under Organization settings, then Connectors, and each member then connects it from Customize, then Connectors, signing in with their own WhichSitesUse account (Anthropic's custom connector docs, checked November 2026). Claude Desktop uses the connectors on your claude.ai account, so there's nothing separate to set up there.

ChatGPT

Custom MCP servers work on ChatGPT on the web, and which plans get them is up to OpenAI. As of November 2026, Business and Enterprise/Edu workspaces get full MCP support, Pro users can connect custom servers with read-only tools, and on Business only admins and owners can add one (OpenAI's help article). Read-only access covers every tool except buy_credits, which ChatGPT treats as a write action because it creates a checkout link.

  1. Go to ChatGPT Plugins, select the plus button, then Add custom MCP server.
  2. Enter WhichSitesUse as the name and, under Connection, https://api.whichsitesuse.com/mcp as the server URL.
  3. Choose OAuth for authentication and leave the client credentials empty, so ChatGPT registers itself.
  4. Review the risk warning, tick I understand and want to continue, then select Create as a plugin and approve the connection on our consent page.
  5. Install the plugin, start a new conversation, type @ and pick WhichSitesUse.

Steps from OpenAI's custom MCP server guide, checked November 2026. ChatGPT asks you to confirm write actions, so expect a prompt before buy_credits runs.

Claude Code

Add the server with an API key from your terminal. Leave out --scope user to add it to the current project only.

claude mcp add --transport http --scope user whichsitesuse \
  https://api.whichsitesuse.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Cursor

Add the server to ~/.cursor/mcp.json to use it in every project, or to .cursor/mcp.json in one project. Reading the key from an environment variable keeps it out of a file you might commit.

{
  "mcpServers": {
    "whichsitesuse": {
      "url": "https://api.whichsitesuse.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:WSU_API_KEY}"
      }
    }
  }
}

Other clients and the REST API

Any MCP client that supports remote Streamable HTTP servers can connect, either with OAuth (authorization code with PKCE, discovered from /.well-known/oauth-protected-resource) or with an API key in a request header. Anything that can make an HTTP request can use the REST API at https://api.whichsitesuse.com/v1 with an API key; each operation below shows its REST method and path.