Skip to main content
Nora ships an MCP server so a coding agent (Claude Desktop, Cursor, Codex, and other MCP hosts) can manage your workspace: create Flows, add Blocks, run and inspect Traces, and publish — all from natural-language instructions. The same commands are available as the nora CLI. MCP is just the coding-agent-friendly way in.

​
What you can do from a coding agent

  • Create or edit a Flow: “Add a Slack Action to the support flow that pings #cx-alerts on refunds.”
  • Connect a data source: “Attach the /policies folder in Drive to the support agent.”
  • Debug: “Pull the last 5 failed traces from support-flow and summarize.”
  • Publish: “Snapshot the draft and publish with note ‘refund tool cleanup’.”

​
Setup — Claude Desktop

  1. In Nora, go to Settings → Personal Access Tokens and click New token. Copy it.
  2. Open Claude Desktop’s MCP settings file:
    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  3. Add the Nora server:
  1. Restart Claude Desktop. In a new chat, you’ll see “nora” appear under available tools.

​
Setup — Cursor

Cursor supports MCP through the same config surface. In Cursor Settings → MCP, add:
Reload Cursor. Nora tools appear in your chat sidebar.

​
Setup — other MCP hosts

Any MCP-capable client works. Point it at @nora-ai/mcp-server via npx and pass NORA_TOKEN in the environment. Full command list matches the CLI Reference.

​
Scoping tokens

Tokens issued from Personal Access Tokens are account-scoped — they can act on any workspace you belong to. For automation, prefer a workspace-scoped token: Settings → Workspace Tokens.
Treat MCP tokens like passwords. Rotate them from the Nora settings page anytime; the old token stops working immediately.

​
What the coding agent can not do

MCP mirrors your permissions. If you’re a Viewer in a workspace, the agent can only read. Approval-gated actions still go through the approval flow — the coding agent cannot bypass them.