Skip to main content
Nora ships an MCP server so a coding agent (Claude Code, Cursor, and other MCP hosts) can manage your workspace: create Flows, add Blocks, run and inspect Traces, and publish, all from natural-language instructions.

​
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 them.”
  • Publish: “Snapshot the draft and publish it with the note ‘refund tool cleanup’.”
  • Explore: “List every Flow in this workspace and tell me which ones have unpublished changes.”

​
Connecting

Nora’s MCP server is a remote HTTP server. There’s no package to install — you just point your host at the URL.
Register the server with claude mcp add. The --transport http flag tells Claude Code to treat this as a remote MCP endpoint rather than a stdio subprocess.
  • --scope user writes it to ~/.claude.json so every project sees Nora. Use --scope project (writes to ./.mcp.json in the repo) when you’d rather share the entry with teammates via git. Omit --scope to keep it local to the current project.
  • The first tool call opens an OAuth login in your browser — sign in with your Nora account and grant read · build · run.
Check that it registered:
Remove it later with claude mcp remove nora.
Both CLI-based hosts (Claude Code, Codex) write the same JSON entry the manual-edit form uses. The mcp add command is just a friendlier surface — no functional difference between the two paths.

​
A separate server per region

Region is decided at login. The regional host you sign in to determines the region. MCP servers are region-specific hosts with separate logins, and each host shows only the workspaces in its region. A Korea workspace won’t appear on the US host, and vice versa. To work across regions, register both servers.
Or, in JSON:
The coding agent sees both, prefixes tool names by server, and works on either. Each server prompts its own OAuth login the first time you use it.

​
What tools MCP exposes

The MCP server surfaces roughly the same operations as the CLI.
  • Flow management (list, get, apply, publish, rollback)
  • Block CRUD (agents, tools, actions, triggers, edges)
  • Data (documents, memory, retrieval, causal, pipelines)
  • Reliability (traces, feedback, approvals)
  • Workspace (providers, connectors, billing)
Each tool has typed inputs, so the coding agent discovers and uses them on its own.

​
Permissions

MCP mirrors your permissions. As a Guest the agent can only read, and actions your role can’t take (see Permissions) stay blocked over MCP too. Approval-gated actions still go through the approval flow when run via MCP.

​
Troubleshooting

  • nora doesn’t appear in the tool list The host didn’t attach the server. Check the URL, and confirm you finished the browser OAuth login.
  • The login window never opens Check the host logs. Confirm the host supports remote MCP and that the URL starts with https://.
  • A region’s workspace is missing Register a server for that region’s host and sign in to that server.

​
Learn more

nora CLI reference

The same operations from the terminal instead of a coding agent

nora auth

CLI login and switching workspaces

MCP on Nora Local

Point your coding agent at a self-hosted Nora instead of platform.nora.my.