Connect a client to this hub

One HTTP endpoint, pasted into your client. There is no API key to paste, no token to copy and no header to set.

The endpoint

Every deployment serves its own hub at the root it runs under:

https://<this host>/mcp

A tenant's own documentation hub gets a dedicated access point instead of the public entry point — its own host, its own brand, its own reader roles:

https://<hub>.<this host>/mcp

The same tool surface answers on both. What differs is which documents are visible and who may read them.

Signing in

Today the read surface is anonymous: a public hub answers without a sign-in, and most of what an agent needs is public. When a hub needs to know who is asking — a private hub, a customer layer — your client opens an account sign-in and keeps the token itself. No page and no document ever shows you a key.

Claude Code

One command, in the project you want it available in:

claude mcp add --transport http cuppy https://<this host>/mcp

Then run /mcp inside Claude Code to confirm the server is connected. If the hub asks who you are, the same /mcp menu opens the sign-in in your browser.

claude.ai

No one-click link is published for claude.ai connectors, so these are the steps:

1. Open Settings → Connectors (https://claude.ai/settings/connectors).
2. Choose Add custom connector.
3. Paste https://<this host>/mcp and save.

ChatGPT

No one-click link is published here either:

1. Open Settings → Connectors (developer mode, where your plan requires it).
2. Add an MCP server and paste https://<this host>/mcp.

Cursor

Cursor publishes an install deeplink of the form cursor://anysphere.cursor-deeplink/mcp/install?name=$NAME&config=$BASE64_ENCODED_CONFIG, where the config is the server's JSON configuration, JSON.stringify-ed and then base64-encoded. The hub's Connect page builds that link for you. By hand:

{
  "mcpServers": {
    "cuppy": { "url": "https://<this host>/mcp" }
  }
}

VS Code

VS Code publishes a URL handler of the form vscode:mcp/install?{json-configuration}, where the JSON configuration is stringified and URL-encoded. The hub's Connect page builds that link too. By hand: add an MCP server, choose HTTP, and enter the endpoint.

{
  "servers": {
    "cuppy": { "type": "http", "url": "https://<this host>/mcp" }
  }
}

Once connected

1. _hello — what this endpoint is and what to read first.
2. the hub's boot document — how this hub is organised, under a token budget.
3. docs search and docs get — the facts your task needs.

Nothing here executes. An operation document renders the request to make; the agent makes it, with its own hands and its own credentials.