For AI agents: a documentation index is available at /llms.txt. A markdown version of this page is available at /guide/mcp/clients.md.

MCPAI Connect

Client setup

Connection settings for Claude, ChatGPT, Cursor, VS Code with GitHub Copilot, the Codex CLI and anything else that speaks remote MCP.

Every client needs the same single value:

bash

https://v4-api.orangescrum.com/mcp/partner

Authentication is OAuth, the client registers itself and opens a browser for you to sign in and pick a workspace. There is no key to paste, and nothing sensitive ends up in the config files below.

Where the token lives

Each client caches its own tokens outside the config file, in the OS keychain, its own profile directory, or ~/.mcp-auth for the mcp-remote bridge. To force a fresh sign-in, remove and re-add the server in the client.

#Claude.ai and Claude Desktop

No config file. Add it as a custom connector:

Open connector settings
Settings → Connectors → Add custom connector.
Paste the URL
Name it Orangescrum and paste https://v4-api.orangescrum.com/mcp/partner.
Connect
Click Connect. The OAuth window opens; sign in, choose a workspace, approve the scopes.

Tip

This is what changed most. Browser-based connectors could not authenticate against the old X-API-KEY endpoint at all. Now they are the easiest path.

#Claude Code

bash

claude mcp add --transport http orangescrum https://v4-api.orangescrum.com/mcp/partner

Then run /mcp inside Claude Code to trigger the sign-in and check the connection status.

#ChatGPT

No config file. Settings → Connectors → Create, paste the same URL, and complete the OAuth prompt.

#Cursor

File: ~/.cursor/mcp.json

json

{
  "mcpServers": {
    "orangescrum": {
      "url": "https://v4-api.orangescrum.com/mcp/partner"
    }
  }
}

Cursor shows the server as needing login in Settings → MCP. Click it to run the OAuth flow.

#VS Code + GitHub Copilot

File: .vscode/mcp.json in your workspace, or the user-level equivalent.

json

{
  "servers": {
    "orangescrum": {
      "type": "http",
      "url": "https://v4-api.orangescrum.com/mcp/partner"
    }
  }
}

VS Code prompts for authentication the first time the server starts. Copilot Chat only exposes MCP tools in agent mode. They will not appear in ask mode.

Tip

This file is now safe to commit: it holds a URL, not a credential. Each teammate signs in as themselves.

#OpenAI Codex CLI

File: ~/.codex/config.toml

toml

[mcp_servers.orangescrum]
url = "https://v4-api.orangescrum.com/mcp/partner"

Check your Codex version

Remote MCP with OAuth is a recent addition to Codex and the exact config key has moved between releases. If your version cannot complete the sign-in, use the bridge below. It works regardless.

#STDIO-only clients

Anything that can only spawn a local process, including older Claude Desktop builds, can reach the server through the mcp-remote bridge, which performs the OAuth flow and caches the tokens in ~/.mcp-auth. Node.js must be installed and on the PATH.

json

{
  "mcpServers": {
    "orangescrum": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://v4-api.orangescrum.com/mcp/partner"
      ]
    }
  }
}

Config file locations for Claude Desktop:

Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Drop the old --header argument

Earlier versions of this page told you to pass --header X-API-KEY:YOUR_KEY. Remove it. The endpoint no longer reads that header, and leaving it in place gets you a 401 with no explanation.

#Any other MCP client

Setting	Value
Transport	Remote HTTP (streamable)
URL	`https://v4-api.orangescrum.com/mcp/partner`
Protocol	JSON-RPC 2.0
Auth	OAuth 2.1 + PKCE, dynamic client registration (RFC 7591)
Auth header	`Authorization: Bearer <token>`
Discovery	`/.well-known/oauth-authorization-server`
Spec revisions	`2025-11-25`, `2025-06-18`, `2025-03-26`, `2024-11-05`

A client that supports remote MCP with OAuth needs nothing but the URL. One that supports remote MCP without OAuth cannot connect directly, put the mcp-remote bridge in front of it.

#Verify the connection

Independent of any client, this proves the endpoint is up and OAuth-protected, 401 with a WWW-Authenticate header is the healthy answer:

bash

curl -i -sS -X POST https://v4-api.orangescrum.com/mcp/partner \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"ping","id":1}'

If that looks right but your client still shows no tools, the problem is in the client. See Troubleshooting.