MCP server

The Norcube MCP server lets AI clients that speak the Model Context Protocol call Norcube tools on your behalf: run a database backup before a deploy, prove a backup restores, check whether a domain is really free. It's a remote server, so there's nothing to install or host.

The tools in this release:

A client only sees the tools its connection's permissions allow: a connection without DomainRadar shows no DomainRadar tools at all. Per-tool details live with each product: Backup MCP tools, DomainRadar MCP tools and LangSync MCP tools. Full restores, deleting backups, backup downloads and the other Norcube products aren't exposed through MCP.

Connect your client

# available in every project
claude mcp add --transport http norcube https://mcp.norcube.com/mcp

# or only in this repository (writes .mcp.json, commit it to share)
claude mcp add --transport http --scope project norcube https://mcp.norcube.com/mcp

https://mcp.norcube.com/mcp

{
  "mcpServers": {
    "norcube": {
      "url": "https://mcp.norcube.com/mcp"
    }
  }
}

https://mcp.norcube.com/mcp

Any other MCP client that supports remote servers with OAuth works the same way: give it the URL and let it run the sign-in.

Sign-in and consent

The first time a client connects, it registers itself with Norcube Auth and opens your browser:

Scopes

Scopes only ever narrow what you can do. Consent can't grant the client more than your own role allows in each organization.

Consent only offers what your role allows

Each permission is offered only if your Norcube role grants the actions behind it in at least one of the organizations you picked:

• Several organizations. A permission your role has in only some of the picked organizations is labelled Only in <org> and works only there. The product checks your role in that organization on every call, so the token can't be used to act elsewhere.
• Not available. Permissions the client asked for but you can't grant appear greyed out as Not available with your role.

Organizations

What you pick on the consent screen decides how tools find their organization:

• One organization (the default): every tool uses it automatically. Tools don't take an organization argument.
• Several organizations: tools take an organization argument (the organization id), and the agent must name one of the organizations you granted. list_organizations returns their ids, names and slugs.

Per-project binding in Claude Code. Add the server with --scope project in each repository and approve a single organization for each. The acme-api repository then always acts on Acme, and your side project on your personal org, without the agent ever choosing.

Permissions, billing and usage

The MCP server holds no business logic. Each tool call is exchanged inside Norcube for a short-lived token for the target product and then calls the same API the dashboard uses, so:

• IAM applies unchanged. If your role can't run a backup in the dashboard, backup_run fails the same way.
• Read-only is enforced twice. A connection without backup.write is refused by the MCP tools, and the Backup API itself also rejects any change made with a read-only connection token. Restore checks need their own backup.verify permission the same way; backup.write alone doesn't allow them.
• The billing gate applies. Organizations that are blocked for an unpaid balance get an error on paid operations, exactly as in the dashboard.
• Usage is metered normally. DomainRadar checks are metered at the usual rates; backups count against your Backup plan, and restore checks work like Test now in the dashboard. Listing stored data (saved domains, bulk checks, brand hits, generated names, backup jobs) costs nothing. There's no separate MCP charge.

Changing a connection's access

Open Account settings → Connected apps in the dashboard and click Edit on a connection. You can add or remove organizations and permissions without reconnecting the client. Edits stay within what the AI client originally asked for and what your role allows.

• Removals take effect on the client's next tool call.
• Additions apply within about 5 minutes, when the client next refreshes its token.
• New permissions available appears when your role now allows something the connection doesn't have yet.
• Permissions your role no longer covers are marked Not available with your current role.
• The client's tool list follows the permissions. After an edit, reconnect the client or reload its tools to see added tools.
• An edit can only add permissions the client asked for when it first connected. If a newer permission (such as Run restore checks) isn't offered for an older connection, remove the server from the client and add it again.

Revoking access

In the same Account settings → Connected apps list, each connected client is shown with its scopes and organizations; Revoke removes it. Revocation takes effect on the client's next tool call, not when a token happens to expire.

Errors you'll see

Tool errors come back as readable messages the agent can relay.

Related

• Backup MCP tools: datasources, on-demand backups, restore checks, the before-deploy workflow.
• DomainRadar MCP tools: live checks, saved domains, brand monitoring and generated names.
• CLI: the same platform from your terminal.
• Members and IAM: the roles every tool call is checked against.