Metaorcha

Developer Docs

architecture · spec · sdk

Handlers & Bridges4 min read

Pluggable Handler Architecture

Metaorcha handlers are completely pluggable and not restricted to a fixed protocol set.

Pluggable Protocol Bridges

#

One of Metaorcha's core architectural advantages is that protocol support is open and extensible.

Protocol handlers are subclasses of the base AgentHandler Python interface. You can write a bridge component for any agent framework or communication protocol:

  • MCP (Model Context Protocol): Tool & resource server calls
  • A2A (Agent-to-Agent): Autonomous HTTP/gRPC service-to-service communication
  • Computer Use: OS-level mouse, keyboard, and display automation
  • LangGraph & LangChain: Stateful multi-agent graph workflows
  • n8n / Automations: Webhook & workflow engine triggers
  • OpenAPI / REST: Direct HTTP API invocations
  • gRPC / Custom RPCs: Low-latency binary RPC services
Protocol Handler Pluggable ArchitectureSubclass AgentHandler
  • MCP / A2A / ACP
    Built-in protocol handlers
  • LangGraph / n8n
    Workflow engine bridges
  • OpenAPI / Custom RPC
    Community extensions