MCP gateway

mcp.clawnify.com is a managed Model Context Protocol gateway that exposes your Clawnify org’s capabilities to any MCP-compatible client.

Officially supports OpenClaw and opencode. Compatible with any MCP agent.

What you can do with it

Once connected, your client sees these tools:

Tool	Purpose
`clawnify.execute`	Run TypeScript on your agent’s managed runtime. Returns stdout / stderr / exit code.
`clawnify.docs_search`	Search across your org’s apps’ procedures. Returns ranked hits with descriptions and snippets.
`clawnify.list_apps`	List the apps in your org.
`clawnify.list_specialists`	List the agents (servers) in your org.
`clawnify.get_usage`	Current plan + quota.
`<slug>.<procedure>`	For apps with five or fewer procedures, each procedure shows up as a direct tool.

Full reference: Tools.

Pick a connection path

Path	Best for
Claude Desktop — download an `.mcpb` bundle, paste your token, done.	Non-technical users who want one-click setup.
Cursor — short JSON snippet in the workspace settings.	Developers in their IDE.
CLI bridge — `clawnify mcp` stdio bridge.	Any bash-capable client. Works with anything that can spawn a subprocess.

How auth works

Every call to mcp.clawnify.com is authenticated. There are two flows:

From your agent itself — uses the agent’s gateway token (set up automatically when the agent is provisioned).
From an external client — uses your personal access token from app.clawnify.com. The CLI handles this transparently after clawnify login; the MCPB bundle prompts you to paste it at install time.

Tokens are scoped to your org. The gateway resolves which org to act on from your account’s membership; multi-org users override per-call via the X-Clawnify-Org-Id header.

Endpoint shape

POST https://mcp.clawnify.com/mcp
Authorization: Bearer <token>
Content-Type: application/json

{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }

Standard MCP Streamable HTTP transport. Notifications (no id) return 202. Everything else returns a JSON-RPC 2.0 response.