MCP

Connecting Nozbe to Claude via MCP

Which setup should I use?

There are three ways to connect Nozbe to Claude. For most people, Option A (Remote MCP via Custom Connector) is the easiest: paste one URL and log in.

The only difference between B and C: in B Nozbe generates the configuration code for you, and you paste it into claude_desktop_config.json. In C you build that code yourself from the template and your own API token.

Option A: Nozbe Remote MCP (Custom Connector) — recommended

Connect Nozbe with a single URL: https://mcp.nozbe.ai/mcp. No config files, no API token, no Node.js.

In Claude (web, desktop or mobile)

1. Open Settings > Connectors.
2. Click Add > Add Custom Connector.
3. Paste https://mcp.nozbe.ai/mcp and confirm.
4. When prompted, choose Log in with Nozbe.
5. You’ll be redirected to nozbe.app in your browser. Authorize the connection.
6. Back in Claude, ask something like “Show my Nozbe tasks for today” to check it works.

In ChatGPT

1. Open Settings > Plugins and click Browse Plugin Directory.
2. Click Add > Add custom MCP server.
3. Fill in the form:
   • Name: Nozbe
   • Connection: https://mcp.nozbe.ai/mcp
   • Authentication: OAuth
4. Review the warning, check I understand and want to continue, then click Create as a plugin.
5. Choose Log in with Nozbe and authorize the connection on nozbe.app.
6. Return to ChatGPT and install the new plugin if prompted.

Nozbe Local MCP (generated config)

Nozbe generates the configuration for you; you only paste it into Claude Desktop. This works in the Claude Desktop app on macOS or Windows, which must be running.

Step 1 — Generate the config in Nozbe

1. In Nozbe, go to Settings > Integrations > MCP > Connect.
2. Choose your agent (Claude Desktop).
3. Copy the generated configuration.

Step 2 — Paste it into Claude Desktop

1. In Claude, open Settings > Desktop app > Extensions.
2. In the Local MCP servers section, click Edit Config. This opens claude_desktop_config.json.
3. Paste the copied configuration inside the mcpServers section. It will look like this (your port number and key will differ):

{
  "mcpServers": {
    "nozbe-local": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://127.0.0.1:<port number>/mcp",
        "--header",
        "Authorization:Bearer nzb_mcp_<key>"
      ]
    }
  }
}

4. Save the file.

Step 3 — Restart and verify

1. Fully quit and reopen Claude Desktop (closing the window is not enough).
2. Go back to Settings > Desktop app > Extensions. Under Local MCP servers, nozbe-local should show as running.

If claude_desktop_config.json already has other servers, add the nozbe-local entry next to them inside the same mcpServers block, separated by a comma.

Nozbe Remote MCP, configured manually (“the old way”)

Same remote server as Option A, but added through Claude Desktop’s config file with your own API token. Use it only if you can’t use the Custom Connector.

Before you begin: Claude Desktop (macOS or Windows) and Node.js 20.18.1 or newer. This doesn’t work in claude.ai on the web.

Step 1 — Create a Nozbe API token

1. In Nozbe, go to Settings > Integrations > API tokens.
2. Create a new token or pick an existing one, and copy it.

Treat the token like a password: anyone who has it can access your Nozbe account. Don’t share your config file with the token in it.

Step 2 — Open Claude’s config file

1. In Claude, open Settings > Desktop app > Extensions.
2. In the Local MCP servers section, click Edit Config.

To find the file manually: on macOS it’s in ~/Library/Application Support/Claude/, on Windows in %APPDATA%\Claude\.

Step 3 — Add the Nozbe server

Add this entry inside mcpServers, replacing <your Nozbe API token> with the token from Step 1:

{
  "mcpServers": {
    "nozbe": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.nozbe.ai/mcp",
        "--header",
        "Authorization:<your Nozbe API token>"
      ]
    }
  }
}

Save the file.

Step 4 — Restart and verify

1. Fully quit and reopen Claude Desktop.
2. Open Settings > Desktop app > Extensions. nozbe should appear under Local MCP servers as running.
3. Ask Claude to list your Nozbe tasks to confirm.

Other clients: Claude Code and Cursor

Claude Code — Local MCP

1. In Nozbe, go to Settings > Integrations > MCP > Connect > Claude Code and copy the command.
2. Run it in your terminal.

Claude Code — Remote MCP with an API token

claude mcp add --transport http nozbe https://mcp.nozbe.ai/mcp \
  --header "Authorization: <your Nozbe API token>"

Cursor — Remote MCP with an API token

1. Open Cursor’s MCP setup form and add a new server.
2. Fill in: Name nozbe, Type URL, Server URL https://mcp.nozbe.ai/mcp, Header Authorization with your Nozbe API token as the value.
3. Click Save Changes.

Or click Edit JSON and paste this (Cursor uses url + headers, not mcp-remote):

{
  "mcpServers": {
    "nozbe": {
      "url": "https://mcp.nozbe.ai/mcp",
      "headers": {
        "Authorization": "<your Nozbe API token>"
      }
    }
  }
}

Troubleshooting (Options B and C)

If the Nozbe server shows an error or never appears as running, click View Logs next to it in Settings > Desktop app > Extensions to see the exact error. The usual causes:

• Node.js missing or too old. npx mcp-remote needs Node.js 20.18.1 or newer. Check with node --version. Install the current LTS from nodejs.org (or brew install node on macOS, winget install OpenJS.NodeJS.LTS on Windows), then fully quit and reopen Claude.
• Invalid JSON in the config file. A missing or extra comma, unbalanced brackets, a leftover <placeholder>, a // comment, or a second mcpServers block all stop the server from loading. Check the file in a JSON validator or an editor like VS Code.
• Claude not fully restarted. Quit the app completely, not just the window.
• Token or key no longer valid. Create a new API token (Option C) or generate a fresh config in Nozbe (Option B).

You can also paste the View Logs error or your config file (with the token removed) into a Claude chat and ask it to find the problem.

Sources

• Nozbe & MCP
• Work smarter with Nozbe AI
• Connecting Claude to the Nozbe MCP Server (PDF)