MCP Setup Guide

Choose the client you use. Each card links to its Remote MCP setup. See MCP for how the connection works and which tools are available once you’re connected.

Claude Code CLI Codex CLI, app & IDE Cursor Editor VS Code Editor Claude.ai / Desktop Web, desktop & mobile ChatGPT Web & desktop GitHub Copilot CLI Terminal agent GitHub Copilot coding agent Cloud coding agent

Claude Code

Authentication: browser sign-in

Choose one setup option. Installing the plugin is recommended. Use manual setup only when you cannot install it.

/plugin marketplace add Bekind-Labs/tracker-boot-ai-plugin
/plugin install tracker-boot@tracker-boot

claude mcp add \
  --transport http \
  --client-id 4litco754ka2pbhl20br7kuvno \
  --callback-port 9876 \
  tracker-boot \
  https://trackerboot.com/mcp

After either option Sign in

Adding Tracker Boot registers the server, but does not connect it automatically:

1. Enter /mcp in Claude Code.
2. Find plugin:tracker-boot:tracker-boot in the plugin server group, or tracker-boot with your own servers if you used manual setup.
3. Select the server and choose Authenticate. Complete Tracker Boot sign-in in the browser.
4. Return to /mcp and confirm that the server changed from needs authentication to connected and its tools are listed.

The sign-in callback uses port 9876. If that port is already in use, stop the process using it and retry.

Codex

Authentication: browser sign-in

Choose one setup option. Installing the plugin is recommended. Both options finish with the same sign-in steps.

codex plugin marketplace add Bekind-Labs/tracker-boot-ai-plugin
codex plugin add tracker-boot@tracker-boot

mcp_oauth_callback_port = 5555

mcp_oauth_callback_port = 5555

[mcp_servers.tracker-boot]
url = "https://trackerboot.com/mcp"

[mcp_servers.tracker-boot.oauth]
client_id = "3eka95setkmhu91vistcfqnq4o"

After either option Sign in

Adding Tracker Boot registers the server, but does not connect it automatically:

1. Enter /mcp and confirm that tracker-boot is listed.
2. Make your first Tracker Boot MCP request. Codex opens the browser for you to sign in.
3. Complete Tracker Boot sign-in, return to Codex, and enter /mcp again.
4. Confirm that the server changed from needs authentication to connected and its tools are listed.

Cursor

Authentication: browser sign-in

Choose one setup option. The one-click installer is recommended. Manual setup is available as a fallback.

{
  "mcpServers": {
    "tracker-boot": {
      "url": "https://trackerboot.com/mcp",
      "auth": {
        "CLIENT_ID": "12v726ksihp2qhdt1js8obt0j0"
      }
    }
  }
}

Continue to After you sign in: grant project access.

VS Code

Authentication: browser sign-in

Add the server

Remote MCP requires VS Code 1.102 or later (July 2025).

1. Open the Command Palette and select MCP: Add Server….
2. Choose HTTP.
3. Enter https://trackerboot.com/mcp.
4. When VS Code shows Dynamic client registration not supported, enter 3orjeoc4ui782rb25jt7henoa7 as the OAuth Client ID and leave the client secret blank.
5. Continue from the dialog. VS Code opens the browser during MCP: Add Server…; complete Tracker Boot sign-in there.
6. Return to VS Code and confirm that the server changed from needs authentication to connected and its tools are listed.

VS Code uses port 33418 for the OAuth callback. If the port is busy, stop the process using it and retry.

Claude.ai / Claude Desktop

Authentication: browser sign-in

Choose one setup option. Installing the plugin is recommended. Adding a custom connector is the manual alternative.

After either option Sign in

1. Open Customize → Connectors.
2. Find Tracker Boot and select Connect.
3. Complete Tracker Boot sign-in in the browser.
4. Return to Customize → Connectors and confirm that Tracker Boot is connected and its tools are listed.

Claude.ai, Claude Desktop, and Claude mobile apps share the connector through your Claude account.

ChatGPT

Remote setup is not available yet. Each ChatGPT connector is issued its own OAuth callback URL, but Tracker Boot must register that URL in advance and Cognito requires an exact match. ChatGPT cannot use the local server alternative because a web client cannot start a local process.

GitHub Copilot CLI

Authentication: API key

Add the server with an API key

Browser sign-in is not available for Copilot CLI because its OAuth callback port changes every time it launches. Create a project-restricted API key in Tracker Boot General Settings → API, then add the hosted server:

copilot mcp add tracker-boot https://trackerboot.com/mcp \
  --type http \
  --header "X-API-KEY=YOUR_TRACKER_BOOT_API_KEY"

Verify the connection:

copilot mcp list

Copilot may display OAuth: needs authentication because Tracker Boot advertises OAuth discovery. The X-API-KEY connection still works; do not start OAuth sign-in.

The key is stored in plaintext in ~/.copilot/mcp-config.json. Restrict the file so only your user account can read it:

chmod 600 ~/.copilot/mcp-config.json

GitHub Copilot coding agent

Authentication: API key

Configure the repository

You need repository administrator access.

1. Open the repository on GitHub and go to Settings → Copilot → MCP servers.
2. Add the configuration below and save it.
3. Add an Agents secret named COPILOT_MCP_TRACKER_BOOT_API_KEY containing a project-restricted Tracker Boot API key. GitHub exposes only secrets with the COPILOT_MCP_ prefix to the coding agent.

{
  "mcpServers": {
    "tracker-boot": {
      "type": "http",
      "url": "https://trackerboot.com/mcp",
      "headers": {
        "X-API-KEY": "$COPILOT_MCP_TRACKER_BOOT_API_KEY"
      },
      "tools": ["*"]
    }
  }
}

The coding agent uses the hosted endpoint. GitHub’s cloud agent does not support OAuth MCP servers, so browser sign-in is not used.

After you sign in: grant project access

Signing in creates the connection, but a new connection has no project access by default:

1. Try a Tracker Boot tool. The first call is denied and tells you to open Tracker Boot General Settings → API.
2. Open General Settings → API, find the new connection, choose the projects it may use, and save.
3. Retry the tool call. It works on the next call; you do not need to sign in again.

Each client type appears as its own connection, so you can grant or revoke access independently. Revoke a browser-sign-in connection from General Settings → API when you no longer use that client.

For Copilot CLI and the coding agent, create a separate project-restricted API key for each client instead of a browser-sign-in connection.

Troubleshooting

The Claude Code plugin fails to install

If you maintain or inspect the plugin marketplace, a relative plugin source in marketplace.json must be written as ./plugins/<name>. A bare name is treated as a remote source and the install fails.

Claude Code reports “Conflicting scopes”

A server named tracker-boot already exists in another Claude Code scope. Remove the duplicate from the scope named in the diagnostic, then retry:

claude mcp remove <name> -s <scope>

Security notes

• Browser-sign-in clients do not store a Tracker Boot credential on disk.
• API keys are secrets. Never commit them, paste them into chat, or expose them in browser-side code.
• Prefer project-restricted API keys for headless clients and revoke the old key when rotating it.
• MCP access never exceeds the signing-in user’s own Tracker Boot permissions.

Appendix: Local MCP with Docker (alternative)

The local server is an alternative for offline, air-gapped, or self-managed environments. It runs on your computer, communicates over stdio, and authenticates with a Tracker Boot API key.

Get an API key from Tracker Boot General Settings → API, keep it private, and pull the latest image:

docker pull public.ecr.aws/tracker-boot/mcp-server:latest

Claude Code CLI

claude mcp add tracker-boot \
  --env TRACKER_BOOT_API_KEY=YOUR_TRACKER_BOOT_API_KEY \
  -- docker run -i --rm \
  -e TRACKER_BOOT_API_KEY \
  public.ecr.aws/tracker-boot/mcp-server:latest

Codex config.toml

Add the following to ~/.codex/config.toml:

[mcp_servers.tracker-boot]
command = "docker"
args = [
  "run", "-i", "--rm",
  "-e", "TRACKER_BOOT_API_KEY",
  "public.ecr.aws/tracker-boot/mcp-server:latest"
]

[mcp_servers.tracker-boot.env]
TRACKER_BOOT_API_KEY = "YOUR_TRACKER_BOOT_API_KEY"

Cursor

Create .cursor/mcp.json:

{
  "mcpServers": {
    "tracker-boot": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TRACKER_BOOT_API_KEY",
        "public.ecr.aws/tracker-boot/mcp-server:latest"
      ],
      "env": {
        "TRACKER_BOOT_API_KEY": "YOUR_TRACKER_BOOT_API_KEY"
      }
    }
  }
}

VS Code

Create .vscode/mcp.json:

{
  "servers": {
    "tracker-boot": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TRACKER_BOOT_API_KEY",
        "public.ecr.aws/tracker-boot/mcp-server:latest"
      ],
      "env": {
        "TRACKER_BOOT_API_KEY": "YOUR_TRACKER_BOOT_API_KEY"
      }
    }
  }
}

GitHub Copilot coding agent

{
  "mcpServers": {
    "tracker-boot": {
      "type": "local",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TRACKER_BOOT_API_KEY",
        "public.ecr.aws/tracker-boot/mcp-server:latest"
      ],
      "env": {
        "TRACKER_BOOT_API_KEY": "$COPILOT_MCP_TRACKER_BOOT_API_KEY"
      },
      "tools": ["*"]
    }
  }
}

Claude.ai and ChatGPT cannot use this mode because web clients cannot start a local process.