Early bird discounts live! Claim your offer

Connecting Claude

Connect Claude (claude.ai, Claude Desktop and Claude Code) to the Subscriby MCP server by signing in, or with a personal access token.

Claude reaches Subscriby as a connector: you give it the server URL, it sends you to Subscriby to sign in, and you approve the connection. Connectors are shared across claude.ai and Claude Desktop on the same account, so you set one up once.

Requirements

  • A Claude plan that allows custom connectors (Pro, Max, Team or Enterprise; on Team and Enterprise an admin may need to enable them).
  • A Subscriby account. The connection acts as you, on the team you are working in.

Add the connector

In claude.ai or Claude Desktop open Settings → Connectors, choose Add custom connector, and enter:

  • Name: Subscriby
  • Remote MCP server URL: https://mcp.subscriby.net — exactly this, no trailing slash

Save it, then press Connect.

Sign in and authorize

Claude opens Subscriby in your browser. Sign in if you are not already (two-factor and passkeys apply as usual), read the consent screen — it names the client, the account you are signed in as and what the connection can do — and press Authorize. You are sent back to Claude and the connector shows as connected.

Access renews itself for as long as you keep using the connection; a connection you stop using for 30 days expires on its own. Disconnecting in Settings → Connectors ends it immediately.

Verify

Open a fresh chat, make sure the Subscriby connector is enabled for it (the tools menu in the composer), and ask:

List my Subscriby projects.

Claude calls list_projects and renders the answer. Read tools run as you ask; tools that change or delete data ask you to confirm inside Claude before they run.

Claude Code

From a terminal:

claude mcp add --transport http subscriby https://mcp.subscriby.net

Then run /mcp inside Claude Code and pick Authenticate next to subscriby; the same browser sign-in and consent screen follow.

Using a personal access token instead

If you would rather the connection carry only the abilities you choose — read-only, or one project — mint a token in Settings → API Tokens and configure Claude with it as a header instead of signing in.

In Claude Code:

claude mcp add --transport http subscriby https://mcp.subscriby.net \
  --header "Authorization: Bearer sbt_live_YOUR_TOKEN"

In Claude Desktop through claude_desktop_config.json (macOS ~/Library/Application Support/Claude/, Windows %APPDATA%/Claude/), using the mcp-remote bridge, because the config file speaks stdio:

{
  "mcpServers": {
    "subscriby": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.subscriby.net",
        "--header",
        "Authorization:${AUTH_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "Bearer sbt_live_YOUR_TOKEN"
      }
    }
  }
}

Keep the token inside env.AUTH_TOKEN, not inline in args. On Windows, npx splits arguments on whitespace — embedding Bearer <token> directly breaks the header. The ${AUTH_TOKEN} placeholder is expanded by mcp-remote after the args are parsed, preserving the space.

Fully quit and relaunch Claude Desktop after editing the file; MCP servers are loaded at launch. When the token rotates, mint a new one, replace the value, relaunch.

Troubleshooting

  • The connector will not connect: the URL must be https://mcp.subscriby.net with nothing after it. Claude compares it to the address the server publishes and refuses a mismatch.
  • Sent to the dashboard but no consent screen: you were asked to sign in first; complete the sign-in and Claude retries the authorization.
  • Tools vanished after a while: Claude renews access silently; if the renewal failed, disconnect and connect again from Settings → Connectors.
  • A 403 on one tool with a personal access token: it lacks that tool's ability; the error names it in error.context.required_ability.
  • Logs: Claude Desktop keeps MCP logs under Developer → MCP → View logs.

Security tip

An OAuth connection never puts a secret on your disk. A personal access token in a config file is plaintext: treat it as you would any credential file — filesystem ACLs, no screen recording while the config is open, and rotate it when the laptop changes hands.

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request