Client Setup

Professional

Use the endpoint and snippets shown in Dashboard > MCP Access. Local, preview, and production endpoints are different, so copy the values from the environment you are testing.

Recommended OAuth Setup

Open Dashboard > MCP Access.
Keep OAuth selected as the connection method.
Copy the MCP endpoint shown on the page.
Pick the client tab and copy the generated setup snippet.
Start the client’s sign-in flow.
After the first successful MCP call, the OAuth connection appears on the MCP Access page.

Codex

Codex should use Algo Trade Analytics’s Client ID Metadata Document URL as the OAuth client identifier. Do not paste a bearer token, pass a fixed Auth0 application client ID, or pre-list local callback URLs on the primary OAuth path.

Before logging in, configure Codex to store MCP OAuth credentials in local files. Add this top-level setting to ~/.codex/config.toml before any [mcp_servers.*] table, creating the file if needed:

mcp_oauth_credentials_store = "file"

Restart Codex after editing the config, then continue with the OAuth commands. File-backed storage avoids repeated macOS Keychain prompts for Codex MCP Credentials after Always Allow, but it stores MCP OAuth credentials in Codex’s local files. Protect ~/.codex like other local secrets.

codex mcp add algo-trade-analytics \
  --url <MCP endpoint copied from Algo Trade Analytics> \
  --oauth-client-id <Client ID Metadata Document URL copied from Algo Trade Analytics>

codex mcp login algo-trade-analytics \
  --scopes mcp:read,mcp:research:write,mcp:candidate:write,mcp:memory:write,offline_access

codex mcp login prints an authorization URL. Complete the OAuth flow in the browser profile that is signed in to the Algo Trade Analytics account you want to use. offline_access lets the client receive a refresh token for long research sessions; it does not grant additional Algo Trade Analytics MCP tool permissions.

If Codex OAuth is still noisy or blocked on a target machine, use the Manual Bearer Fallback below for Codex until the local credential-store issue is resolved.

Claude.ai Cowork, Claude.ai, and Claude Desktop

Claude.ai Cowork, Claude.ai, and Claude Desktop use Claude’s connector/settings UI. Do not paste a CLI setup block into a Cowork chat and expect the assistant to register or authenticate the connector.

Add a remote connector with these values:

Connector name: Algo Trade Analytics
Connector type: Remote HTTP MCP
Connector URL: <MCP endpoint copied from Algo Trade Analytics>
Authentication: OAuth

Claude discovers Algo Trade Analytics’s protected-resource metadata and Client ID Metadata Document from the MCP URL, then handles OAuth in-app. Use the plain MCP endpoint URL exactly as shown in Algo Trade Analytics. Do not wrap it in Markdown brackets.

After the connector shows Connected, ask Cowork:

Use the algo-trade-analytics connector and list the available tools.

Surfaces that accept JSON config should still use a plain URL:

{
  "mcpServers": {
    "algo-trade-analytics": {
      "type": "http",
      "url": "<MCP endpoint copied from Algo Trade Analytics>"
    }
  }
}

Claude Code

Claude Code registers remote MCP servers from the terminal, then authenticates through /mcp. It uses Algo Trade Analytics’s Client ID Metadata Document path; do not pass a bearer token, fixed Auth0 client ID, or pre-listed local callback URL.

# Current project only. Run this from the project folder where you want the MCP server registered.
claude mcp add --transport http algo-trade-analytics \
  <MCP endpoint copied from Algo Trade Analytics>

# User scope. Use this when you want the server available across projects.
claude mcp add --scope user --transport http algo-trade-analytics \
  <MCP endpoint copied from Algo Trade Analytics>

After claude mcp add, Claude Code can show Needs authentication. That is expected. Run /mcp, choose Authenticate, and complete OAuth. After sign-in the status should change to Connected.

Cursor and ChatGPT

Add Algo Trade Analytics as a remote HTTP MCP server using the endpoint from the MCP Access page. Choose OAuth when the client offers an authentication method. Do not add an Authorization header for OAuth setup.

{
  "mcpServers": {
    "algo-trade-analytics": {
      "type": "http",
      "url": "<MCP endpoint copied from Algo Trade Analytics>"
    }
  }
}

OpenAI API / Studio

Studio and API workflows do not complete remote OAuth on behalf of your Algo Trade Analytics account. Use the manual path and provide the bearer value from a secret.

export ATA_MCP_TOKEN="<MCP access token>"

{
  "type": "mcp",
  "server_label": "ata",
  "server_description": "Algo Trade Analytics research context and strategy evidence tools.",
  "server_url": "<MCP endpoint copied from Algo Trade Analytics>",
  "authorization": "Bearer ${ATA_MCP_TOKEN}",
  "require_approval": "always",
  "allowed_tools": ["ata_context"]
}

Manual Bearer Fallback

Use manual API keys only when the client cannot complete OAuth or when you are working with API-side MCP calls that need an explicit authorization value.

Open Dashboard > MCP Access.
Switch the connection method to Manual API key.
Create a token with the narrowest scopes required for your client.
Copy the token before leaving the page. Algo Trade Analytics shows the full token only once.
Store the token in an environment variable or secret manager. Do not commit it to config files.

Codex Manual Fallback

export ATA_MCP_TOKEN="<MCP access token>"

[mcp_servers."algo-trade-analytics"]
url = "<MCP endpoint copied from Algo Trade Analytics>"
bearer_token_env_var = "ATA_MCP_TOKEN"

Stdio-Only Bridge

Use a bridge only when the host cannot connect to a remote HTTP MCP server directly.

{
  "mcpServers": {
    "algo-trade-analytics": {
      "command": "uvx",
      "args": [
        "fastmcp-remote",
        "<MCP endpoint copied from Algo Trade Analytics>",
        "--header",
        "Authorization: Bearer <MCP access token>"
      ]
    }
  }
}

OAuth and CIMD Why OAuth clients should discover metadata instead of using fixed client IDs

Security, Scopes, and Credits How scopes, revocation, and Algo Trade Analytics credits apply to MCP