Skip to main content

MCP Adapter

The MCP adapter lets a venue call external Model Context Protocol (MCP) servers as grid operations — discovering their tools and invoking them like any other operation.

Looking for the other direction — exposing your venue's operations to an AI assistant as MCP tools? A venue is automatically an MCP server. See Venues as MCP Servers.

Operations​

OperationCatalog pathPurpose
mcp:tools:listv/ops/mcp/tools-listList the tools a remote MCP server offers
mcp:tools:callv/ops/mcp/tools-callInvoke a tool on a remote MCP server
mcp:tool:addv/ops/mcp/add-toolCurate a single remote tool as a catalog operation at a path you choose
mcp:server:addv/ops/mcp/add-serverMirror all of a server's tools into the catalog
mcp:server:removev/ops/mcp/remove-serverRemove a mirrored server's tools and registry entry
mcp:server:refreshv/ops/mcp/refreshRe-sync bridged tools against the live server (mirror or curated mode)

A server is addressed by URL or by DID (resolved from the DID document's service entries). See Calling MCP Tools for worked examples, authentication options, and orchestration patterns.

Bridging: remote tools as catalog operations​

Beyond one-off calls, the adapter can bridge remote MCP tools into the operation catalog, where they behave exactly like native operations — capability grants, gates, job records, schema validation, and agent tool palettes all apply. Curate individual tools from different servers into groups at catalog paths of your choosing, or mirror a whole server. See Calling MCP Tools § Bridging for the full guide.

Why go through the Grid?​

Calling an MCP server through a venue, rather than wiring it into your client directly, gives you:

  • Plug-and-play orchestration — compose MCP tools with other grid operations, agents, and orchestrations.
  • A system of record — every call is a Job with an auditable record on your venue.
  • Controlled credentials — API keys live in the venue's secret store, not in the client.