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 gets tools for:
| Area | Tools | What for |
|---|---|---|
| Apps | clawnify_list_apps, clawnify_get_app, clawnify_create_app, clawnify_update_app, clawnify_publish_app, clawnify_delete_app, clawnify_app_api_read, clawnify_app_api_write, clawnify_app_api_delete, clawnify_docs_search | Build, change, and publish apps, and call their APIs. |
| Integrations | clawnify_list_integrations, clawnify_find_actions, clawnify_action | Act in the services your org has connected: send the email, add the row. |
| Company Knowledge | company_knowledge_search, company_knowledge_get, company_knowledge_list, company_knowledge_propose, plus tools to write, publish, and review documents | Your org’s source of truth, with citations. |
| Projects | projects_list, project_search, project_list_documents, project_add_document | Working reference for one client or engagement. |
| Memory | memory_recall, memory_write, plus tools to list, pin, and delete memories | What your agents have learned and should keep. |
| Tasks | tasks_list, tasks_create, tasks_update, tasks_complete, tasks_delete | The org’s Tasks board. An agent starts on a task as soon as it is assigned one. |
| Agents | clawnify_list_agents, plus tools to read an agent’s sessions, transcripts, skills, and instructions, and to rewrite its AGENTS.md | See what an agent did, and fix its instructions. |
| Flows | clawnify_list_flows, clawnify_get_flow, clawnify_write_flow, clawnify_publish_flow, clawnify_run_flow, clawnify_get_flow_runs | Author, publish, and run ClawFlow automations. |
| Code | clawnify_execute | Run TypeScript on your agent’s runtime. Off until an owner or admin turns it on. |
| Account | clawnify_get_usage, clawnify_list_orgs | Your current plan, and which organization to act on when you belong to several. |
Which of these a client sees depends on how it signs in: see Who can call what.
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: signs in as you (the CLI after
clawnify login, or an OAuth connector such as Claude or ChatGPT), or uses an access token from Settings → Access tokens. The MCPB bundle prompts you to paste a token 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.