Claude

Connect Claude to your Naumu spaces over MCP so it can search, read, and build your memory as you.

Updated August 5, 20262 min read

You can connect Claude (claude.ai) to your Naumu account so it can work directly with your spaces.

This works through a remote MCP server. MCP (Model Context Protocol) is the open standard that AI apps use to reach outside tools, and Naumu runs one so Claude can plug in.

Once connected, Claude acts on your behalf - as the signed-in Naumu user, with your exact permissions. It can do anything you can do across the spaces you have access to, and nothing more. You grant access by approving it on a consent screen (powered by OAuth 2.1, the standard sign-in protocol), and you can revoke that access at any time.

The connector URL

The connector URL is always the Naumu front-end origin - the same naumu.ai address you use in your browser:

Code
https://naumu.ai/api/mcp

You never need an OAuth Client ID or Secret. Both are optional, and Claude keeps them tucked under Advanced settings - you can leave that section closed. Naumu registers the app for you automatically during sign-in, using a feature called Dynamic Client Registration (DCR), so there are no credentials to copy or manage.

Use the front-end origin (naumu.ai), not a backend address. Sign-in and consent rely on your Naumu session, which lives on the front-end origin.

Connect Claude

In Claude (claude.ai):

  1. Open Settings → Connectors (under Customize in the settings sidebar).
  2. Select Add, then Add custom connector.
  3. Give it a name (for example, "Naumu").
  4. Set Remote MCP server URL to https://naumu.ai/api/mcp.
  5. Leave Advanced settings closed - the optional Client ID and Secret stay blank.
  6. Select Add.
  7. Sign in to Naumu and approve access on the consent screen.

That's it - Naumu's tools are now available in Claude.

What it can access

A connected app can use your full set of Naumu tools, across every space your account can reach. Specifically, it can:

  • Search and read content across your spaces
  • Read your spaces, nodes, threads, notes, and canvases
  • Create and update content - nodes, threads, notes, canvases, and more

Because Claude acts as you, it inherits your permissions exactly. It cannot see or change anything you couldn't see or change yourself.

Revoke access

You can cut off Claude's access at any time in Naumu, under Settings → Your agents, in the Active access list. Revoking takes effect immediately - the app can no longer reach your spaces.

Revoking is the clean way to disconnect. You don't need to delete the connector in Claude first. Once you revoke the access here, any further requests from that app are rejected.

  • ChatGPT - connect ChatGPT the same way, over MCP.
  • Local MCP - connect coding agents like Claude Code and Cursor over the same remote MCP server.
  • Spaces - the workspaces a connected client reads and writes.
Anything missing?
Tell us what would make these docs better.