MCP Client

Agenvoy's MCP client lets agents call tools exposed by any MCP server. Client and server share one package (internal/runtime/mcp) built on the official modelcontextprotocol/go-sdk.

Configuration layout

One file. The session-scoped layer was removed — every client reads the same config:

~/.config/agenvoy/mcp.json

JSON format

{
  "servers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": { "GITHUB_TOKEN": "${GITHUB_TOKEN}" }
    },
    "remote-api": {
      "url": "https://api.example.com/mcp",
      "headers": { "Authorization": "Bearer ${TOKEN}" }
    }
  }
}

command and url are mutually exclusive. ${VAR} / $VAR placeholders inside env, headers, and args are expanded with os.Expand at startup.

Transport types

Both transports are handled by the SDK; Agenvoy only supplies the command or the endpoint plus a header-injecting HTTP client.

Management

The add flow asks for the server name, transport (Local stdio / Remote HTTP), and the type-specific fields. There are no agen mcp CLI subcommands.

OAuth for HTTP servers

A server marked auth: oauth logs in through mcp.Login: the daemon opens a loopback callback listener on localhost:17988, performs dynamic client registration when the provider allows it, and stores the resulting token and client id in the OS keychain. When the provider rejects dynamic registration, supply a pre-registered client with POST /v1/mcp/oauth/client (redirect_uri defaults to http://localhost:17988/callback and must match the provider console exactly). When the browser cannot reach the listener, paste the redirect URL back with POST /v1/mcp/oauth/callback.

Tool naming

MCP-exposed tools are auto-registered with the format:

mcp__<server_name>__<tool_name>

Example: mcp__github__create_issue, mcp__sqlite-notes__read_query.

Result size cap

Each MCP tool result is capped at 1 MiB. When exceeded, the result is truncated with the marker:

[mcp output truncated: <total> bytes total, <kept> kept]

This avoids OpenAI Responses API's 10 MB single-tool-output limit triggering a same-signature retry storm. SQLite SELECT * on a large table will hit this — add LIMIT / WHERE.

Confirm behavior

MCP tools route through the most conservative defaults:

• Every MCP tool call goes through the same confirm gate as a built-in tool, under whatever permission mode the request carries
• No per-server read_only toggle — Agenvoy does not extend trust to third-party servers because their behavior is unverifiable (a Slack MCP could silently send messages, a Filesystem MCP could silently write files)

Trust is granted per tool, not per server: /mcp → server → tools (or POST /v1/allowlist with a tool block) replaces the auto-approve entries for one prefix, leaving unrelated rules alone. Every entry must start with that prefix, and prefix* collapses the rest into a whole-server grant. The list lives in ~/.config/agenvoy/allow_tool.

Lifecycle

• Startup: app.NewMCP calls mcp.New(ctx, sid), then RegisterAll(ctx), then starts Watch(ctx), before the agent registry is built; clients close on shutdown
• Live tool refresh: clients subscribe to the server's notifications/tools/list_changed and re-register that server's tools when its catalog changes — no restart needed for a server that adds or drops tools
• Server instructions: whatever a server declares as its instructions is surfaced into the agent system prompt, so per-server usage rules reach the model
• Per-server failures: a start or tool-list failure logs a warning and skips that server; core functionality never blocks
• Manual recovery: POST /v1/mcp/reconnect reconnects every client and re-registers tools; /mcp → server → reconnect in the TUI does the same for one server

Recommended servers

Zero-auth, locally executed (no API key required):

Avoid registering MCP servers whose capabilities overlap with built-in tools (e.g., filesystem, git, fetch, shell) — duplicates only inflate the LLM tool list.