Connecting ChatGPT Desktop
Configure ChatGPT Desktop's MCP support to work with Subscriby.
Requirements
- ChatGPT Desktop with MCP support (macOS or Windows builds that have the MCP feature flag on).
- A Subscriby token carrying
mcp:fulland the per-entity read abilities you want the assistant to use.
Config
ChatGPT Desktop reads MCP servers from its Settings → Connectors → Developer panel. Add a new connector with:
- Name:
subscriby - Server URL:
https://mcp.subscriby.net - Auth: Bearer token → paste the
sbt_…token
ChatGPT will negotiate the MCP handshake and list all available tools in the connector panel.
Test
Open a fresh chat with the subscriby connector enabled (toggle icon in the chat 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.
Token scope tips
ChatGPT Desktop tends to invoke multiple tools per turn. For read-only exploratory chats, mint a token with only view-any + view abilities. For "build me a plan" workflows, add project-subscription-plan:create. Avoid granting write abilities you don't want the assistant to exercise without explicit approval.
Troubleshooting
- Connector disabled: enable it in the composer toolbar for the current chat.
- Auth failed: the Subscriby server returns 401 with a clear error. Re-mint the token.
- Tool 403s: the token is missing the ability that specific tool enforces — the error envelope includes
required_abilityto make fixing it fast.
How is this guide?