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​

OperationPurpose
mcp:tools:listList the tools a remote MCP server offers
mcp:tools:callInvoke a tool on a remote MCP server

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

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.