MCP (Model Context Protocol) + AGNT
The open standard for exposing tools to LLMs — AGNT speaks MCP natively.
Official sourceWhat it is
Model Context Protocol is an open standard for exposing structured tools to language models. A tool has a name, input schema, output schema, and handler — and any MCP-compatible client can call it without writing provider-specific adapter code.
MCP is not owned by any single vendor. Claude supports it natively. Other providers are converging. The protocol ships over SSE (Server-Sent Events), which makes real-time tool responses straightforward.
Where AGNT fits
- AGNT runs an MCP server at `/mcp/sse` exposing venue search, listing, and booking confirmation as native tools. Any MCP-capable LLM can call these directly. No REST wrapping, no custom client library, no schema translation.
- AGNT is also an MCP host — it can consume external MCP servers and surface their tools inside the AGNT agent runtime. Your MCP server for Linear / GitHub / Stripe becomes callable from an AGNT venue agent without writing Python.
- The composition pattern: AGNT's memory + graph + commerce surface is one MCP server. Your infra + observability tools are another. A single Claude Code or AGNT session can reason over both.
Integration recipes
Build an MCP server exposing AGNT wiki + graph
Ship a custom MCP server wrapping AGNT's wiki + graph endpoints, callable from any MCP client.
Wire AGNT memory into Claude Code as an MCP server
The reference walkthrough — Claude Code as MCP client, AGNT as MCP server.
Stream Hermes outputs into AGNT heartbeat logs
Use MCP as the bridge between a Hermes router session and AGNT's heartbeat stream.