Cursor

Cursor speaks MCP natively. The shortest path is the Clawnify CLI’s mcp subcommand — it bridges stdio to mcp.clawnify.com and reuses your clawnify login credentials.

Install

1. CLI

npm install -g clawnify
clawnify login

2. Cursor config

Cursor reads MCP servers from ~/.cursor/mcp.json (global) or .cursor/mcp.json in a workspace.

{
  "mcpServers": {
    "clawnify": {
      "command": "clawnify",
      "args": ["mcp"]
    }
  }
}

Reload Cursor. The Clawnify tools (clawnify.execute, clawnify.docs_search, plus any per-app direct tools from your org) appear in the agent panel.

Verify

In a new Cursor chat:

List the tools you have available from Clawnify, then call clawnify.execute with the code: console.log(1 + 1)

You should see the tool list and then 2 in the execute result.

Troubleshooting

  • “command not found: clawnify” — install location not in PATH. Use the full path in the command field, e.g. /Users/you/.nvm/versions/node/v22/bin/clawnify.
  • “Not logged in” errors — run clawnify login first. The bridge reads stored credentials; no separate auth.
  • No org context — make sure your account has an active org. Multi-org users can scope a specific org by adding CLAWNIFY_ORG_ID to the bridge’s env ("env": { "CLAWNIFY_ORG_ID": "..." }).