Connecting ChatGPT Desktop

Configure ChatGPT's connectors to work with Subscriby, by signing in or with a personal access token.

Requirements

ChatGPT with developer mode connectors enabled (Plus, Pro, Team, Enterprise or Edu; on a workspace plan an admin may need to allow them).
A Subscriby account. ChatGPT signs you in; a personal access token is only needed when you want a connection narrower than your own reach.

Add the connector

Open Settings → Connectors → Create (developer mode) and enter:

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

Save. ChatGPT opens Subscriby in your browser: sign in if you are not already, read the consent screen and press Authorize. ChatGPT negotiates the MCP handshake and lists the tools in the connector panel.

Test

Open a fresh chat with the Subscriby connector enabled (toggle icon in the composer) and ask:

List my Subscriby projects.

The response includes which tool was invoked. If the call fails, inspect the error — every Subscriby MCP error carries a docs_url pointing back to this documentation.

Using a personal access token instead

Choose Authentication: No authentication on the connector, and add a custom header Authorization with the value Bearer sbt_… from a token minted in Settings → API Tokens. ChatGPT then skips the sign-in and the connection carries only the abilities you ticked.

Scope tips

ChatGPT tends to invoke multiple tools per turn. For read-only exploratory chats, a personal access token with only view-any + view abilities keeps the assistant from writing anything. For "build me a plan" workflows the OAuth connection is simpler; every tool that changes or deletes data is marked destructive, so ChatGPT asks before running it.

Troubleshooting

Connector disabled: enable it in the composer toolbar for the current chat.
Sign-in never completes: the URL must be exactly https://mcp.subscriby.net; finish the browser sign-in and try connecting again.
Auth failed after a while: disconnect and reconnect the connector to sign in again; with a personal access token, re-mint it.
Tool 403s with a personal access token: the token is missing the ability that specific tool enforces — the error envelope includes required_ability to make fixing it fast.