The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Subscriby listing page.
Connect Claude, Cursor, VS Code and other MCP clients to your Subscriby workspace.
Subscriby is a connector-based community monetisation platform — creators sell access to the channels, groups and servers a connector gates, with projects, tiered subscriptions, access codes, and analytics. Learn more at subscriby.net.
159 tools across your own account (who the token belongs to, its team, plan capabilities, connected accounts and alert routing, the notification centre), the Connectors Marketplace (every connector in its lane, what each can do and the form that connects it) and a project's connector installations (read them with their health; install, verify, configure, disconnect, and uninstall them after an impact preview), projects, plans and pass windows, subscriptions and their access grants, the hand-arranged perks still to deliver, the Disaster Recovery ledger (incidents, recoveries and their undo state, roll calls, allowances, readiness) and its controls (failover settings, standbys and their mirror, chat pickers, undo, reminders, the handover mail), coupons, subscriptions, members and their connected accounts, the support inbox (conversations, saved replies, settings), access codes, payment methods, payments, broadcasts, resources, bots, teams, webhook endpoints and deliveries, and analytics. See the full catalog at docs.subscriby.net/mcp/v1/tools-reference. Every tool declares whether it only reads or may change data, so a client can ask before running a destructive one.
Add https://mcp.subscriby.net as a custom connector in claude.ai or Claude Desktop, or run claude mcp add --transport http subscriby https://mcp.subscriby.net in Claude Code, then sign in when asked. Follow docs.subscriby.net/mcp/v1/connecting-claude-desktop.
Follow docs.subscriby.net/mcp/v1/connecting-cursor.
Follow docs.subscriby.net/mcp/v1/connecting-vscode-claude.
Follow docs.subscriby.net/mcp/v1/connecting-chatgpt-desktop.
Two credentials work on the same endpoint:
401 challenge, registers itself dynamically (RFC 7591) and sends you to Subscriby to sign in and authorize; PKCE S256 is required, access tokens last an hour and refresh tokens rotate. The connection acts as you, on the team you are working in. Nothing to copy.Authorization: Bearer sbt_…, minted at https://app.subscriby.net/settings/tokens with only the abilities and team scope you choose.See docs.subscriby.net/mcp/v1/authentication.
Every tool enforces one ability; an OAuth connection satisfies them all as the signed-in creator, a personal access token only those it carries. See docs.subscriby.net/api/v1/abilities.
See docs.subscriby.net/api/v1/rate-limiting.
See docs.subscriby.net/api/v1/errors.
See docs.subscriby.net/mcp/v1/async-jobs.
See SECURITY.md.
See CHANGELOG.md. The version field in server.json is the canonical version published to the MCP Registry.
MIT.