Connection

AgentPMT exposes one MCP server for your Agent Group. Use the hosted Streamable HTTPS endpoint when your client supports remote MCP. Use the local STDIO router when your client requires a command-based MCP server.

The Bearer token belongs to one Agent Group. The tools, credentials, spending caps, and activity log for that group define what the connected agent can do.

Prerequisites

1. Create or choose an Agent Group

   In the dashboard, open Control Center -> Agent Groups. Add the tools and workflows this agent may use, bind required credentials, and set spend controls.

2. Copy the Bearer token

   Click Show Bearer Token on the group card. Treat the token like a password; it authorizes every MCP call for that group.

3. Choose a transport

   Prefer hosted Streamable HTTPS for remote-MCP clients. Choose local STDIO only when the client needs a local command.

Hosted Streamable HTTPS Endpoint

Endpoint:  https://api.agentpmt.com/mcp
Transport: Streamable HTTP over HTTPS
Auth:      Authorization: Bearer <AGENTPMT_BEARER_TOKEN>

Hosted MCP does not require a local package. Your client connects directly to AgentPMT over HTTPS, sends the Bearer token in config or a secret field, and receives the current tool catalog for the agent group.

Complete Hosted Config Examples

Use this generic shape for MCP clients that accept remote Streamable HTTP servers in a config file:

{
  "mcpServers": {
    "agentpmt": {
      "type": "streamable-http",
      "url": "https://api.agentpmt.com/mcp",
      "headers": {
        "Authorization": "Bearer <AGENTPMT_BEARER_TOKEN>",
        "x-instance-metadata": "{\"client\":\"generic-mcp\",\"platform\":\"remote\"}"
      }
    }
  }
}

x-instance-metadata is optional. When your client supports custom headers, use it to identify the client and platform in activity logs.

URL: https://api.agentpmt.com/mcp
Authorization: Bearer <AGENTPMT_BEARER_TOKEN>

Server URL: https://api.agentpmt.com/mcp
Authentication: Bearer token
Bearer token: <AGENTPMT_BEARER_TOKEN>

URL: https://api.agentpmt.com/mcp
Header: Authorization: Bearer <AGENTPMT_BEARER_TOKEN>
Optional header: x-instance-metadata: {"client":"postman","platform":"desktop"}

Local STDIO Fallback

Install the local router when your MCP client requires a command. The router does not execute tools locally. It reads AGENTPMT_BEARER_TOKEN, receives JSON-RPC over STDIO, and forwards requests to https://api.agentpmt.com/mcp.

npm install -g @agentpmt/mcp-router
agentpmt-setup

The setup command detects supported clients, asks for the Bearer token, and writes the appropriate config. Re-run agentpmt-setup when you switch agent groups or add another local client.

Platform-Specific Local Config Examples

Use these blocks only for clients that need a local command. Keep AGENTPMT_BEARER_TOKEN in the config file or the client secret store. X_INSTANCE_METADATA is optional and must be a JSON string.

{
  "mcpServers": {
    "agentpmt": {
      "command": "npx",
      "args": ["--package=@agentpmt/mcp-router@latest", "agentpmt-router"],
      "env": {
        "AGENTPMT_BEARER_TOKEN": "<AGENTPMT_BEARER_TOKEN>",
        "X_INSTANCE_METADATA": "{\"client\":\"claude_desktop\",\"platform\":\"desktop\"}"
      }
    }
  }
}

{
  "mcpServers": {
    "agentpmt": {
      "command": "npx",
      "args": ["--package=@agentpmt/mcp-router@latest", "agentpmt-router"],
      "env": {
        "AGENTPMT_BEARER_TOKEN": "<AGENTPMT_BEARER_TOKEN>",
        "X_INSTANCE_METADATA": "{\"client\":\"claude_code\",\"platform\":\"cli\"}"
      }
    }
  }
}

{
  "mcpServers": {
    "agentpmt": {
      "command": "npx",
      "args": ["--package=@agentpmt/mcp-router@latest", "agentpmt-router"],
      "env": {
        "AGENTPMT_BEARER_TOKEN": "<AGENTPMT_BEARER_TOKEN>",
        "X_INSTANCE_METADATA": "{\"client\":\"cursor\",\"platform\":\"desktop\"}"
      }
    }
  }
}

{
  "mcpServers": {
    "agentpmt": {
      "command": "npx",
      "args": ["--package=@agentpmt/mcp-router@latest", "agentpmt-router"],
      "env": {
        "AGENTPMT_BEARER_TOKEN": "<AGENTPMT_BEARER_TOKEN>",
        "X_INSTANCE_METADATA": "{\"client\":\"vscode\",\"platform\":\"desktop\"}"
      }
    }
  }
}

{
  "mcpServers": {
    "agentpmt": {
      "command": "npx",
      "args": ["--package=@agentpmt/mcp-router@latest", "agentpmt-router"],
      "env": {
        "AGENTPMT_BEARER_TOKEN": "<AGENTPMT_BEARER_TOKEN>",
        "X_INSTANCE_METADATA": "{\"client\":\"windsurf\",\"platform\":\"desktop\"}"
      }
    }
  }
}

{
  "context_servers": {
    "agentpmt": {
      "settings": {},
      "command": {
        "path": "npx",
        "args": ["--package=@agentpmt/mcp-router@latest", "agentpmt-router"],
        "env": {
          "AGENTPMT_BEARER_TOKEN": "<AGENTPMT_BEARER_TOKEN>",
          "X_INSTANCE_METADATA": "{\"client\":\"zed\",\"platform\":\"desktop\"}"
        }
      }
    }
  }
}

[mcp_servers.agentpmt]
command = "npx"
args = ["--package=@agentpmt/mcp-router@latest", "agentpmt-router"]

[mcp_servers.agentpmt.env]
AGENTPMT_BEARER_TOKEN = "<AGENTPMT_BEARER_TOKEN>"
X_INSTANCE_METADATA = '{"client":"codex","platform":"cli"}'

{
  "mcpServers": {
    "agentpmt": {
      "command": "npx",
      "args": ["--package=@agentpmt/mcp-router@latest", "agentpmt-router"],
      "env": {
        "AGENTPMT_BEARER_TOKEN": "<AGENTPMT_BEARER_TOKEN>",
        "X_INSTANCE_METADATA": "{\"client\":\"gemini\",\"platform\":\"cli\"}"
      }
    }
  }
}

Browser-Based Clients

Use the hosted endpoint for browser clients that support remote MCP connectors. Store the Bearer token in the connector's secret/auth field, not in a chat message.

If the browser client does not support remote MCP, use AgentPMT's direct HTTP API from your own server-side runtime instead of exposing the Bearer token in client-side code.

Postman Testing

Postman is useful for verifying an agent group before you rely on an agent prompt.

1. Create an MCP request

   Choose Postman's MCP request type and set the URL to https://api.agentpmt.com/mcp.

2. Add auth and metadata

   Add Authorization: Bearer <AGENTPMT_BEARER_TOKEN>. Optionally add x-instance-metadata: {"client":"postman","platform":"desktop"}.

3. Connect and run a tool

   Connect, choose one of the loaded tools, fill in the displayed parameters, and run the request.

4. Verify activity

   Open Control Center -> Agent Activity and confirm the request, response, status, and metadata are logged.

Troubleshooting

Discovery and Protocol Reference

curl -X POST "https://api.agentpmt.com/mcp" \
  -H "Authorization: Bearer <oauth_access_token>" \
  -H "Content-Type: application/json" \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "initialize",
  "params": {
    "protocolVersion": "2025-03-26",
    "clientInfo": {
      "name": "agentpmt-docs-example-client",
      "version": "1.0.0"
    },
    "capabilities": {
      "tools": {}
    }
  }
}'

curl -X POST "https://api.agentpmt.com/mcp" \
  -H "Authorization: Bearer <oauth_access_token>" \
  -H "Content-Type: application/json" \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list",
  "params": {}
}'

curl -X POST "https://api.agentpmt.com/mcp" \
  -H "Authorization: Bearer <oauth_access_token>" \
  -H "Content-Type: application/json" \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "<tool_name_from_tools_list>",
    "arguments": {
      "example_input": "value"
    }
  }
}'

curl -X GET "https://www.agentpmt.com/api/external/tools?limit=20"

curl -X POST "https://www.agentpmt.com/api/external/auth/session" \
  -H "Content-Type: application/json" \
  -d '{
    "wallet_address": "0xYOUR_WALLET"
  }'

curl -X POST "https://www.agentpmt.com/api/external/tools/<product_slug>/actions/<action_slug>/invoke" \
  -H "Content-Type: application/json" \
  -d '{
    "wallet_address": "0xYOUR_WALLET",
    "session_nonce": "<session_nonce>",
    "request_id": "<unique_request_id>",
    "signature": "0x<wallet_signature>",
    "parameters": {
      "example": "value"
    }
  }'

Related API Reference Links

Raw Bearer-token API callers should use Programmatic Access. Wallet-authenticated autonomous agents should use the Autonomous Agents API. Agents paying for one eligible tool action with direct x402 should use X402 Payments For Tool Usage.