Module mcp

Modules§

auth: Auth material resolution for remote MCP endpoints.
client: MCP client over the Streamable HTTP transport. No local process is ever spawned: a server is reached over a socket or not at all.
elicit: Elicitation → ask_human: letting an MCP server ask the operator.
http: The MCP Streamable HTTP client transport.
mock_http: A minimal built-in Streamable HTTP MCP server, for tests and for operators kicking the tyres on reactive setups. Hidden mode: agentd --internal-mock-mcp-http <addr-file> <uri> [--no-emit].
pace: The service pace registry behind a catalog entry’s rate:: one process-global map, seeded at the from_spec chokepoint — the ONLY place every process (reactor, turn worker, flat subagent) constructs its MCP clients — so a rated catalog entry paces its consumers wherever the call actually executes. Buckets are keyed by SERVICE name rather than by server, so every server referencing one entry shares a single bucket per process.

from_spec: Build an MCP client from a declared crate::config::McpServerSpec: resolve its secret-free {{secret:…}} auth header templates (via auth) and connect to the spec’s remote endpoint, stamping agentd’s client identity. The config/auth-coupled counterpart of the crate’s transport-only client::McpClient::connect. Call initialize on the result before use.