ClawQLProtocol Fabric

Any protocol in. Any protocol out. MCP in the middle.

Core turns APIs into MCP tools. mcp-api-adapter turns MCP back into OpenAPI, GraphQL, gRPC, CLI, WebSocket, QR, or /mcp-ui. One common IR — both directions.

Read the Fabric docs Start free trial

Architecture

Seven in. Hub. Seven out.

API sources on the left, ClawQL Core + mcp-api-adapter at the center, transport layers on the right. WORM audit and HTMX / MCP-UI sit under the hub — every hop is agent-native and auditable.

ClawQL Protocol Fabric — seven API sources into ClawQL Core + mcp-api-adapter, seven transport layers out, WORM audit log and HTMX / MCP-UI below the hub — ClawQL Protocol Fabric — anything to MCP to anything

Both directions

N×M protocols collapse to N+M

Enterprise service buses reduced integrations with a common bus. Protocol Fabric is the agent-era analogue: MCP is the message format, full protocol surface on both sides.

ClawQL Core → MCP

REST · GraphQL · gRPC · WebSocket · MCP · generated CLI · QR stream

Out

mcp-api-adapter → any surface

OpenAPI · GraphQL · Streamable HTTP · gRPC · gen-cli · WebSocket · QR · /mcp-ui

Proven loop

WebSocket → CLI → REST → vault — one smoke

August 2026: a deterministic path crosses both fabric directions and lands a real vault note. Not an LLM benchmark — if any hop fails, the marker never shows up in recall.

WebSocket event
    → mcp-api-adapter (/ws tools/call)
    → clawql-mcp execute(cli__fabric_event__run)
    → gen-cli subprocess
    → POST /memory_ingest on the adapter (REST)
    → clawql-mcp memory_ingest
    → vault note with marker FABRIC_LOOP_*
    → memory_recall finds the marker

Run it from the repo: scripts/dev/smoke-protocol-fabric-loop.sh. Full write-up on the Protocol Fabric docs.

Connected products

Fabric is the spine — Streams and Agents ride it

Same MCP endpoint, same vault, same adapter surfaces. Streams adds the event loop. Agents add significance filters, ontology recall, and human review via /mcp-ui.

Protocol Fabric specification — architecture, loop topology, competitive framing
mcp-api-adapter — wrap any MCP server; expose OpenAPI, GraphQL, gRPC, CLI, WebSocket
Custom sources — CLI / OpenAPI / GraphQL / gRPC ops into Core
ClawQL Streams — event-driven autonomous agents on the fabric
Agentic Platform — Streams + ontology + TEE-ready audit

Put MCP between your protocols

Self-host free on Apache 2.0, or start a 14-day Developer trial. One MCP endpoint on every tier — same URL when you upgrade.

Start free trial Read the Fabric docs