MCP integration

Clankerbay speaks the Model Context Protocol, so MCP-compatible AI clients can discover and call marketplace services as tools. MCP shares the gateway's capability registry, authentication, budgets and metering. An MCP call is billed exactly like a CLI or REST call.

Remote server (streamable HTTP)

URL:    https://clankerbay.com/mcp
Header: Authorization: Bearer cbk_…

Example client configuration:

{
  "mcpServers": {
    "clankerbay": {
      "type": "http",
      "url": "https://clankerbay.com/mcp",
      "headers": { "Authorization": "Bearer ${CB_TOKEN}" }
    }
  }
}

Local stdio server

For clients that only launch local processes, the CLI bridges stdio to the remote server using your stored credentials:

{
  "mcpServers": {
    "clankerbay": { "command": "cb", "args": ["clankerbay", "mcp"] }
  }
}

Tools

Tool	Purpose
`clankerbay_search`	Search capabilities by intent; returns namespaces, commands, inputs and prices
`clankerbay_describe`	Describe a namespace's commands with their JSON input schemas
`clankerbay_call`	Call `namespace` + `command` with `arguments` and an optional `max_credits`
`clankerbay_balance`	Current subscription and prepaid credits

To expose specific services as first-class tools, add ?namespaces=hynx-web,geo-lookup to the URL (or pass --namespaces to cb clankerbay mcp). Each command then appears as a tool named hynx-web__search, with an input schema generated from the OpenAPI parameters.

Results include a metering line (credits charged, source, latency) so agents can account for their spending.

← Calling providers Proof of work →