MCP is the standard. Agiorcx is the operating system.
Wrap any MCP server as an Agiorcx tool. Expose any Agiorcx agent as an MCP server. Both directions, clean interfaces.
Complementary. Not competing.
MCP defines how tools are described and called. Agiorcx SDK decides when to call them, coordinates agents, enforces state, and attributes failures.
They are complementary, not competing. MCP is a protocol — a standard for describing capabilities and invoking them across process boundaries. Agiorcx is the coordination layer — the runtime that decides which agent needs which capability, when to invoke it, what policy governs the invocation, and what happens when it fails. You need both. @agiorcx/mcp is the bridge.
- Tool description schema
- Capability discovery
- Cross-process tool invocation
- Standard request/response format
- When to call which tool
- Agent-level policy enforcement
- State management and transitions
- Failure attribution and audit trail
- Multi-agent coordination across tools
Two adapters. Both directions.
Any MCP server → Agiorcx ToolAdapter
Wrap any MCP-compatible server as an Agiorcx ToolAdapter. The adapter handles capability discovery, maps the MCP schema to Agiorcx's typed tool interface, and routes invocations through the SDK's policy layer. Your agents call it as a standard Agiorcx tool — the MCP protocol is transparent.
Any Agiorcx agent → MCP server
Expose any Agiorcx agent as a standards-compliant MCP server. Any MCP-compatible client — another agent framework, a Claude integration, a custom orchestrator — can discover and invoke your agent's capabilities without knowing anything about the Agiorcx SDK. The agent remains fully governed: policy still applies, every invocation is still logged.