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. |
company_knowledge_search | Search your org’s Company Knowledge (policy, pricing, brand, SOPs, FAQs) and get cited answers. |
company_knowledge_get | Read one Company Knowledge document in full by id. |
projects_list | List the Projects mounted on the agent (client / engagement / capability scopes). |
project_search | Search within one Project for scoped working reference. |
memory_recall | Search the agent’s long-term memory store and return the most relevant durable memories. |
memory_write | Save a durable memory (preference, commitment, fact) to the agent’s long-term store. |
<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 afterclawnify 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.