Connect a client

Pick the client you use. Hosted assistants sign in with your Monotree account. Coding agents and scripts use an API token instead.

Replace customer with your company's Monotree subdomain in every example.

Sign-in clients

These clients open a browser window where you sign in with your Monotree account. Available to admins, editors and managers.

Claude

Web, desktop and mobile. Go to Settings → Connectors → Add custom connector, paste https://customer.monotree.com/mcp, then click Connect and sign in. Or use the shortcut on Getting started, which opens that dialog with the connector filled in.

In a Claude Team or Enterprise organization an owner can add the connector once for everyone under Admin settings → Connectors; members then enable it from their own settings.

ChatGPT

Go to Settings → Apps & Connectors → Create, paste the URL and complete the sign-in. Custom connectors may require developer mode or a workspace plan; check OpenAI's current requirements.

In a ChatGPT Business or Enterprise workspace an admin can add Monotree once for the whole workspace: Workspace settings → Permissions & roles → Connected data → Custom MCP connectors, then create the connector with the URL, scan its tools, test it as a draft and publish it. Members then sign in with their own Monotree account the first time they use it.

Gemini

Go to Settings → Extensions, add the server URL and sign in.

Other sign-in clients

Any MCP client that supports OAuth with a https:// callback on claude.ai, claude.com, chatgpt.com, chat.openai.com or gemini.google.com, or a http://localhost callback, can register itself automatically. Clients with other callback domains cannot register yet; use an API token or contact Monotree. See Authorization.

Token clients

Coding agents and automations authenticate with an Open API token. An admin creates one under Open API → AI Connectors → Create MCP token. It comes pre-loaded with the scopes the tools use and acts as the admin who created it.

Claude Code

claude mcp add --transport http monotree https://customer.monotree.com/mcp \
  --header "Authorization: Bearer mono_your_token_here"

Cursor

Add to .cursor/mcp.json in your project, or the global Cursor MCP settings:

{
  "mcpServers": {
    "monotree": {
      "url": "https://customer.monotree.com/mcp",
      "headers": { "Authorization": "Bearer mono_your_token_here" }
    }
  }
}

VS Code

Add to .vscode/mcp.json:

{
  "servers": {
    "monotree": {
      "type": "http",
      "url": "https://customer.monotree.com/mcp",
      "headers": { "Authorization": "Bearer mono_your_token_here" }
    }
  }
}

Gemini CLI

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "monotree": {
      "httpUrl": "https://customer.monotree.com/mcp",
      "headers": { "Authorization": "Bearer mono_your_token_here" }
    }
  }
}

Gemini CLI can also sign in through the browser, since it uses a localhost callback.

Microsoft Copilot Studio

Add the server as an MCP tool with the server URL, choose API key authentication, and send the token in the Authorization header as Bearer mono_your_token_here. Copilot Studio cannot sign in with a Monotree account, so the assistant acts as the admin who created the token.

Your own agent or script

The server speaks MCP over streamable HTTP. A plain JSON-RPC POST works without a session handshake. The Accept header must include text/event-stream.

curl -X POST https://customer.monotree.com/mcp \
  -H "Authorization: Bearer mono_your_token_here" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_handbooks","arguments":{}}}'

Use "method":"tools/list" to see the tools your token can call. Tool errors keep HTTP 200; check result.isError and read result.content[0].text.

Clients without sign-in

Some clients cannot sign in with a Monotree account and must use a token instead:

• Microsoft Copilot Studio registers with a client secret, which the automatic registration does not issue. Use the token setup above.
• Native desktop clients that register with a custom URL scheme (cursor://, vscode://). Use the token setup above.