MCP Tool Bridge

Yaha exposes federated MCP tools at POST /mcp/v1 (Streamable HTTP). Use the same yaha.* key as LLM traffic.

Supported agents in this integration set: Cline, Continue CLI, Hermes Agent.

Prerequisites

Project gateway key (yaha.*)
Tool Bridge enabled on the project (Yaha console → Tool Bridge)
At least one registry item (upstream MCP server) and policy (all enabled or capability group)

See MCP_FLOW.md for architecture.

Connection details

Setting	Value
MCP URL	`https://gateway.yahagateway.io/mcp/v1`
Authorization	`Bearer yaha.<your-project-key>`
Protocol	MCP Streamable HTTP (`initialize`, `tools/list`, `tools/call`)

Tool names are namespaced as serverName/toolName (e.g. mock-mcp/ping).

Per-client configuration

Cline

Cline extension → MCP settings → add remote server:

URL: https://gateway.yahagateway.io/mcp/v1
Headers: Authorization: Bearer yaha.*

Continue CLI

In ~/.continue/config.yaml:

mcpServers:
  - name: nova
    command: npx
    args: ["-y", "mcp-remote", "https://gateway.yahagateway.io/mcp/v1"]
    env:
      AUTHORIZATION: Bearer yaha.<your-project-key>

Hermes Agent

Configure MCP server URL and bearer token in ~/.hermes/config.yaml per Hermes MCP documentation, using the same URL and key as above.

LLM proxy tool loop (optional)

Apps using /v1/chat/completions without client-side tools can opt into Yaha orchestration:

X-Yaha-Tools: enabled

This is separate from external MCP clients; agent CLIs typically run their own tool loops.

Troubleshooting

Issue	Check
`401 unauthorized`	Valid `yaha.*`; Tool Bridge enabled on project
Empty tool list	Registry items seeded; capability group allowlist
Tools fail at runtime	Upstream MCP server health (`GET .../registry/{id}/health`)