MCP server documentation

Claude Code

Run once in a terminal; Claude Code stores the server in your user-level config.

claude mcp add --transport http --scope user agilehero https://api.agilehero.io/mcp \
  --header "Authorization: Bearer <YOUR_TOKEN>"

Use an environment variable instead

export AGILEHERO_MCP_TOKEN=<YOUR_TOKEN>
claude mcp add --transport http --scope user agilehero https://api.agilehero.io/mcp \
  --header 'Authorization: Bearer ${AGILEHERO_MCP_TOKEN}'

• All flags must come before the server name.

Verify: Run claude mcp list — agilehero should show as connected. If it connects but lists no tools, update Claude Code (older builds dropped custom headers).

Claude Code documentation · verified against the vendor docs on 2026-09-09

Cursor

Add to ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one project.

~/.cursor/mcp.json

{
  "mcpServers": {
    "agilehero": {
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Use an environment variable instead

{
  "mcpServers": {
    "agilehero": {
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer ${env:AGILEHERO_MCP_TOKEN}" }
    }
  }
}

Verify: Open Cursor → Settings → MCP: agilehero should be switched on and list its tools.

Cursor documentation · verified against the vendor docs on 2026-09-09

VS Code (GitHub Copilot)

Add to .vscode/mcp.json in a workspace, or run "MCP: Open User Configuration" for all workspaces.

.vscode/mcp.json

{
  "servers": {
    "agilehero": {
      "type": "http",
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Prompt for the token instead of storing it in the file

{
  "inputs": [
    {
      "type": "promptString",
      "id": "agilehero-token",
      "description": "AgileHero MCP token",
      "password": true
    }
  ],
  "servers": {
    "agilehero": {
      "type": "http",
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer ${input:agilehero-token}" }
    }
  }
}

• "type": "http" is required — without it VS Code treats the URL as a command to run.

Verify: Run "MCP: List Servers", start agilehero, and check that its tools appear in the Chat view.

VS Code (GitHub Copilot) documentation · verified against the vendor docs on 2026-09-09

Codex

Add to ~/.codex/config.toml — shared by the Codex CLI, the IDE extension, and the ChatGPT desktop app.

~/.codex/config.toml

[mcp_servers.agilehero]
url = "https://api.agilehero.io/mcp"
http_headers = { Authorization = "Bearer <YOUR_TOKEN>" }

Use an environment variable instead

# shell profile
export AGILEHERO_MCP_TOKEN=<YOUR_TOKEN>

# ~/.codex/config.toml
[mcp_servers.agilehero]
url = "https://api.agilehero.io/mcp"
bearer_token_env_var = "AGILEHERO_MCP_TOKEN"

• Restart Codex after editing the file.

Verify: Restart Codex and ask it to list your AgileHero projects — the first successful call confirms the connection.

Codex documentation · verified against the vendor docs on 2026-09-09

Claude Desktop

Claude Desktop reaches remote servers through the mcp-remote bridge in claude_desktop_config.json (needs Node.js).

claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "agilehero": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.agilehero.io/mcp", "--header", "Authorization:${AGILEHERO_AUTH}"],
      "env": { "AGILEHERO_AUTH": "Bearer <YOUR_TOKEN>" }
    }
  }
}

• Keep Authorization:${AGILEHERO_AUTH} without a space after the colon — the bridge splits arguments on spaces, and the environment variable carries the space inside its value.
• Custom connectors (Settings → Connectors → Add custom connector) can take the token as a request header, but that option is in beta for a limited set of organizations. When you see a "Request headers" section: URL https://api.agilehero.io/mcp, Authentication "None", header authorization = Bearer <your token>. Never enter one token for a whole organization — every call runs as the token's owner.

Verify: Restart Claude Desktop — agilehero appears in the tools menu of a new chat.

Claude Desktop documentation · verified against the vendor docs on 2026-09-09

Gemini CLI

Add to ~/.gemini/settings.json, or add it from the terminal.

~/.gemini/settings.json

{
  "mcpServers": {
    "agilehero": {
      "httpUrl": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Or add it from the terminal

gemini mcp add --transport http --header "Authorization: Bearer <YOUR_TOKEN>" agilehero https://api.agilehero.io/mcp

• Use httpUrl, not url — url selects the legacy SSE transport.

Verify: Run /mcp inside Gemini CLI — agilehero should be listed with its tools.

Gemini CLI documentation · verified against the vendor docs on 2026-09-09

Zed

Add to settings.json, or use Settings → AI → MCP Servers → Add Remote Server.

~/.config/zed/settings.json

{
  "context_servers": {
    "agilehero": {
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Verify: Restart Zed and ask it to list your AgileHero projects — the first successful call confirms the connection.

Zed documentation · verified against the vendor docs on 2026-09-09

Cline

Add to Cline's MCP settings (MCP Servers panel → Configure), or ~/.cline/mcp.json for the CLI.

cline_mcp_settings.json

{
  "mcpServers": {
    "agilehero": {
      "type": "streamableHttp",
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

• "type": "streamableHttp" is required — without it Cline falls back to legacy SSE.

Verify: Restart Cline and ask it to list your AgileHero projects — the first successful call confirms the connection.

Cline documentation · verified against the vendor docs on 2026-09-09

OpenCode

Add to opencode.json (project) or the global OpenCode config.

opencode.json

{
  "mcp": {
    "agilehero": {
      "type": "remote",
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" },
      "enabled": true
    }
  }
}

Use an environment variable instead

{
  "mcp": {
    "agilehero": {
      "type": "remote",
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer {env:AGILEHERO_MCP_TOKEN}" },
      "enabled": true
    }
  }
}

Verify: Restart OpenCode and ask it to list your AgileHero projects — the first successful call confirms the connection.

OpenCode documentation · verified against the vendor docs on 2026-09-09

Google Antigravity

Add to ~/.gemini/config/mcp_config.json, or Settings → Customizations → Installed MCP Servers.

~/.gemini/config/mcp_config.json

{
  "mcpServers": {
    "agilehero": {
      "serverUrl": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

• Use serverUrl — url and httpUrl are rejected.

Verify: Restart Google Antigravity and ask it to list your AgileHero projects — the first successful call confirms the connection.

Google Antigravity documentation · verified against the vendor docs on 2026-09-09

Kiro

Add to ~/.kiro/settings/mcp.json (all projects) or .kiro/settings/mcp.json (one project).

~/.kiro/settings/mcp.json

{
  "mcpServers": {
    "agilehero": {
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Verify: Restart Kiro and ask it to list your AgileHero projects — the first successful call confirms the connection.

Kiro documentation · verified against the vendor docs on 2026-09-09

Warp

Paste into Settings → Agents → MCP servers.

{
  "agilehero": {
    "url": "https://api.agilehero.io/mcp",
    "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
  }
}

Verify: Restart Warp and ask it to list your AgileHero projects — the first successful call confirms the connection.

Warp documentation · verified against the vendor docs on 2026-09-09

Amp

Add to ~/.config/amp/settings.json (or .amp/settings.json in a project).

~/.config/amp/settings.json

{
  "amp.mcpServers": {
    "agilehero": {
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Use an environment variable instead

{
  "amp.mcpServers": {
    "agilehero": {
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer ${AGILEHERO_MCP_TOKEN}" }
    }
  }
}

Verify: Restart Amp and ask it to list your AgileHero projects — the first successful call confirms the connection.

Amp documentation · verified against the vendor docs on 2026-09-09

GitHub Copilot CLI

Add to ~/.copilot/mcp-config.json, or .mcp.json inside a repository.

~/.copilot/mcp-config.json

{
  "mcpServers": {
    "agilehero": {
      "type": "http",
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Verify: Restart GitHub Copilot CLI and ask it to list your AgileHero projects — the first successful call confirms the connection.

GitHub Copilot CLI documentation · verified against the vendor docs on 2026-09-09

Roo Code

Add to .roo/mcp.json in a project, or the global mcp_settings.json.

.roo/mcp.json

{
  "mcpServers": {
    "agilehero": {
      "type": "streamable-http",
      "url": "https://api.agilehero.io/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Verify: Restart Roo Code and ask it to list your AgileHero projects — the first successful call confirms the connection.

Roo Code documentation · verified against the vendor docs on 2026-09-09

Raycast AI

Raycast Pro: run "Install MCP Server" and fill in the form.

Transport: HTTP
URL: https://api.agilehero.io/mcp
HTTP headers: Authorization = Bearer <YOUR_TOKEN>

Verify: Restart Raycast AI and ask it to list your AgileHero projects — the first successful call confirms the connection.

Raycast AI documentation · verified against the vendor docs on 2026-09-09

JetBrains AI Assistantvia mcp-remote

Settings → Tools → AI Assistant → Model Context Protocol → add a server that runs the mcp-remote bridge (the remote-server form has no headers field yet). Needs Node.js.

{
  "mcpServers": {
    "agilehero": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.agilehero.io/mcp", "--header", "Authorization:${AGILEHERO_AUTH}"],
      "env": { "AGILEHERO_AUTH": "Bearer <YOUR_TOKEN>" }
    }
  }
}

• Keep Authorization:${AGILEHERO_AUTH} without a space after the colon — the bridge splits arguments on spaces, and the environment variable carries the space inside its value.

Verify: Restart JetBrains AI Assistant and ask it to list your AgileHero projects — the first successful call confirms the connection.

JetBrains AI Assistant documentation · verified against the vendor docs on 2026-09-09

Continuevia mcp-remote

Add a file under .continue/mcpServers/ that runs the mcp-remote bridge (remote servers have no documented headers field). Needs Node.js.

.continue/mcpServers/agilehero.yaml

name: AgileHero
version: 0.0.1
schema: v1
mcpServers:
  - name: agilehero
    command: npx
    args: ["-y", "mcp-remote", "https://api.agilehero.io/mcp", "--header", "Authorization:${AGILEHERO_AUTH}"]
    env:
      AGILEHERO_AUTH: "Bearer <YOUR_TOKEN>"

• Keep Authorization:${AGILEHERO_AUTH} without a space after the colon — the bridge splits arguments on spaces, and the environment variable carries the space inside its value.

Verify: Restart Continue and ask it to list your AgileHero projects — the first successful call confirms the connection.

Continue documentation · verified against the vendor docs on 2026-09-09

Claude.ai and Claude Desktop connectorsbeta

Custom connectors can send the token as a request header. The option is in beta for a limited set of organizations.

Settings → Connectors → Add custom connector
Name: AgileHero
URL: https://api.agilehero.io/mcp
Authentication: None
Request headers: authorization = Bearer <YOUR_TOKEN>

• If there is no "Request headers" section, your organization does not have the beta yet — use Claude Code or the Claude Desktop config file instead.
• Team and Enterprise admins: a connector credential is shared with the whole organization. Do not enter one AgileHero token for everyone — every call runs as that token's owner, with their permissions.

Verify: Start a new chat — AgileHero is listed under connectors once the connector is enabled.

Claude.ai and Claude Desktop connectors documentation · verified against the vendor docs on 2026-09-09

Other client

Any client with remote MCP support needs only the endpoint and the Authorization header. A client that cannot send headers can run the mcp-remote bridge as a local command instead.

npx -y mcp-remote https://api.agilehero.io/mcp --header "Authorization:Bearer <YOUR_TOKEN>"

• Write Authorization:Bearer without a space after the colon when the header is one argument — several clients split arguments on spaces, which silently breaks authentication.

Verify: Restart your client and ask it to list your AgileHero projects — the first successful call confirms the connection.

Other client documentation · verified against the vendor docs on 2026-09-09

ChatGPTnot yet

ChatGPT connectors require OAuth sign-in, which AgileHero does not offer yet. Codex — the CLI, the IDE extension, and the Codex tab of the ChatGPT desktop app — works with a token.

ChatGPT documentation · verified against the vendor docs on 2026-09-09