Skip to main content

Connect AgentDock from different clients

AgentDock connects to Claude Desktop, ChatGPT, Claude Code, Cursor, VS Code, Codex, TRAE, and WorkBuddy over Streamable HTTP MCP. Every example on this page uses:

https://agentdock.example.com/mcp

Replace it with your own AgentDock MCP URL.

note

Menu names, plan restrictions, and workspace policies may change between client releases. This page uses common current labels. When an entry is not visible, search settings for MCP, Plugins, or Connectors.

Before connecting​

For a public client or cloud service, confirm that:

  • AgentDock is available through a public HTTPS domain.
  • The MCP URL ends with /mcp.
  • OAuth is enabled, or the client supports a Bearer Token in an HTTP header.
  • The reverse proxy forwards /mcp, /register, /oauth/*, and /.well-known/*.

OAuth requires at least:

AGENTDOCK_OAUTH_ENABLED=true
AGENTDOCK_SERVER_URL=https://agentdock.example.com
AGENTDOCK_OAUTH_PASSWORD=<authorization-password-at-least-12-characters>
AGENTDOCK_OAUTH_TOKEN_SECRET=<random-signing-key-at-least-32-bytes>

AGENTDOCK_SERVER_URL contains only the origin, without /mcp. The client receives the complete https://agentdock.example.com/mcp URL.

A local client running on the same computer as AgentDock may also connect to:

http://127.0.0.1:8765/mcp

A cloud client cannot reach 127.0.0.1 on your computer or server.

Claude Desktop​

Availability of custom MCP connections and the number of servers you can add depend on the current plan and workspace policy.

  1. Open Claude Desktop and go to Customize > Connectors.

  2. Select +, then Add Connector.

  3. Enter AgentDock as the name.

  4. Enter this MCP Server URL:

    https://agentdock.example.com/mcp

  5. Save and select Connect.

  6. When the browser opens the AgentDock authorization page, enter AGENTDOCK_OAUTH_PASSWORD.

ChatGPT​

The current plan and workspace must support custom MCP plugins. An enterprise workspace may also require an administrator to enable developer mode.

  1. Open ChatGPT and go to Settings > Plugins > Advanced settings.

  2. Enable Developer mode.

  3. Select Create plugin.

  4. Enter AgentDock as the plugin name.

  5. Enter this MCP Server URL:

    https://agentdock.example.com/mcp

  6. Save the plugin and begin the connection.

  7. When the browser opens the AgentDock authorization page, confirm the plugin name and callback domain, then enter AGENTDOCK_OAUTH_PASSWORD.

  8. Return to ChatGPT and confirm that the AgentDock plugin is available.

See Connect ChatGPT to AgentDock for complete endpoint checks and troubleshooting.

Claude Code​

OAuth​

Run:

claude mcp add --transport http agentdock https://agentdock.example.com/mcp

Then run this inside Claude Code:

/mcp

Select AgentDock and complete OAuth authorization in the browser.

Bearer Token​

claude mcp add --transport http agentdock https://agentdock.example.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN_HERE"

Do not leave a real token in shell history, scripts, or a public repository. For long-term use, inject it through a restricted environment variable or the client's secret-management capability.

Cursor​

  1. Open Cursor Settings.
  2. Select Tools & MCP.
  3. Select Add Custom MCP.
  4. Edit .cursor/mcp.json in the project:
{
  "mcpServers": {
    "agentdock": {
      "url": "https://agentdock.example.com/mcp"
    }
  }
}

Return to Tools & MCP, find AgentDock, select Connect, and complete OAuth in the browser.

For a Bearer Token:

{
  "mcpServers": {
    "agentdock": {
      "url": "https://agentdock.example.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Project-level .cursor/mcp.json may be committed to version control. Never place a real token in a file that will be committed.

VS Code​

Create or edit .vscode/mcp.json in the workspace:

{
  "servers": {
    "agentdock": {
      "type": "http",
      "url": "https://agentdock.example.com/mcp"
    }
  }
}

You may also open the command palette:

Ctrl+Shift+P / Cmd+Shift+P

Run Add Server, choose HTTP (HTTP or Server-Sent Events), enter the AgentDock MCP URL and server ID, and choose a workspace or global configuration. Complete OAuth in the browser after saving.

For a Bearer Token:

{
  "servers": {
    "agentdock": {
      "type": "http",
      "url": "https://agentdock.example.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Workspace configuration may enter Git. Do not commit a real token.

Codex​

Codex App​

  1. Open Codex and go to Settings > Plugins > MCP.

  2. Select Add server.

  3. Enter AgentDock as the name.

  4. Choose Streamable HTTP as the transport.

  5. Enter this MCP Server URL:

    https://agentdock.example.com/mcp

  6. Save, select Authenticate, and complete OAuth in the browser.

Command line​

codex mcp add agentdock --url https://agentdock.example.com/mcp

Follow the terminal prompt to complete OAuth login and authorization.

TRAE​

  1. Open TRAE settings.
  2. Select MCP.
  3. Select Add > Add manually.
  4. Add this configuration:
{
  "mcpServers": {
    "agentdock": {
      "url": "https://agentdock.example.com/mcp"
    }
  }
}

After saving, find AgentDock in the installed MCP servers, select Authenticate, and complete OAuth in the browser.

For a Bearer Token:

{
  "mcpServers": {
    "agentdock": {
      "url": "https://agentdock.example.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

WorkBuddy​

  1. Open WorkBuddy and select Skills on the left.
  2. Select MCP Servers on the right.
  3. Select Configure MCP.
  4. Add this configuration:
{
  "mcpServers": {
    "agentdock": {
      "type": "http",
      "url": "https://agentdock.example.com/mcp",
      "disabled": false
    }
  }
}

After saving, return to the MCP list, find AgentDock, select Connect, and complete OAuth in the browser.

For a Bearer Token:

{
  "mcpServers": {
    "agentdock": {
      "type": "http",
      "url": "https://agentdock.example.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      },
      "disabled": false
    }
  }
}

Verify the connection​

Do not stop after the client reports “connected.” Complete a real read-only call, for example:

Call AgentDock's server_info and tell me the service version, operating system, and current authentication mode.

If the OAuth page does not open, verify:

curl -fsS https://agentdock.example.com/.well-known/oauth-authorization-server
curl -fsS https://agentdock.example.com/.well-known/oauth-protected-resource/mcp

A 302 from the authorization page usually means AgentDock is redirecting to the client as expected. If the browser does not continue, confirm that the reverse proxy preserves the Location header and that the browser or network policy does not block the callback URL.

See Configuration for complete authentication settings and Manual Linux deployment for public deployment.