Claude Code

Give Claude Code access to MaestroHub through its MCP server, using a Personal Access Token and your workspace ID.

Config file

.mcp.json in the project root

Endpoint

/api/v1/mcp

Restart

Not needed

Claude Code supports MCP servers via a .mcp.json configuration file.

Configuration

Save the following as .mcp.json in your project root:

{
  "mcpServers": {
    "maestrohub": {
      "type": "http",
      "url": "https://<your-instance>/api/v1/mcp",
      "headers": {
        "Authorization": "ApiKey <your-token>",
        "X-Workspace-ID": "<your-workspace-id>"
      }
    }
  }
}

Replace the placeholders:

• <your-instance>: your MaestroHub domain (e.g., maestro.example.com)
• <your-token>: the Personal Access Token you created
• <your-workspace-id>: your workspace ID (found in the URL or workspace settings)

note

For local deployments without TLS, change https:// to http:// in the URL (e.g., http://localhost:6163/api/v1/mcp).

Add it from the command line

claude mcp add writes the same settings for you:

claude mcp add --transport http --scope project maestrohub https://<your-instance>/api/v1/mcp \
  --header "Authorization: ApiKey <your-token>" \
  --header "X-Workspace-ID: <your-workspace-id>"
claude mcp list

--scope project writes .mcp.json in the current directory. Use --scope user to make MaestroHub available in every project, or leave --scope out to add it for this project on your machine only. claude mcp list shows the server as connected once the URL, token and workspace ID are right.

Tips

• Claude Code reads .mcp.json when a session starts and asks you to approve the server the first time. Start a new session after changing it.
• Add .mcp.json to your .gitignore to avoid committing tokens.