Subscriby

What Subscriby MCP server does

Subscriby MCP server gives MCP-compatible clients access to a Subscriby workspace, a connector-based platform where creators sell access to gated channels, groups, and servers. The server exposes 159 tools covering account information, projects, connector installations, tiered plans, subscriptions, members, payments, support, analytics, and operational recovery workflows.

The available operations span both read and write actions. Clients can inspect connector availability and installation health, preview the impact of connector changes, and then install, verify, configure, disconnect, or uninstall connectors. They can also manage access grants, coupons, access codes, payment methods, broadcasts, resources, bots, teams, webhook endpoints, and webhook deliveries.

How it works

Clients connect to the hosted endpoint at https://mcp.subscriby.net. Authentication supports two paths. OAuth 2.1 lets a client discover the authorization server, register dynamically, and send the user through Subscriby sign-in and authorization. PKCE with the S256 method is required; access tokens last one hour and refresh tokens rotate. The resulting connection acts as the signed-in creator within the selected team.

Alternatively, a personal access token can be sent as a bearer credential. Tokens are created in Subscriby settings and can be limited to selected abilities and a team scope. Every tool enforces an ability, so a token may not be able to run every operation. The documentation also defines rate limits, error responses, and asynchronous job behavior.

Setup and configuration

Subscriby MCP server is configured as a remote MCP connection rather than described as a locally launched process in the provided material. Claude users can add the hosted URL as a custom connector in Claude.ai or Claude Desktop. Claude Code can add it with the HTTP transport and the same endpoint. Separate connection instructions are provided for Cursor, VS Code, and ChatGPT Desktop.

OAuth requires no credential copying: the client starts the authorization flow when prompted. For token-based access, create a personal access token at https://app.subscriby.net/settings/tokens, choosing its abilities and team scope before supplying it to the client.

Tools and capabilities

The tool catalog includes capabilities for:

• Inspecting the current account, team, plan capabilities, connected accounts, alert routing, and notifications.
• Browsing the Connectors Marketplace and managing a project’s connector installations.
• Managing projects, plans, pass windows, subscriptions, access grants, perks, coupons, and access codes.
• Working with members, connected accounts, payment methods, payments, broadcasts, resources, bots, and teams.
• Handling support conversations, saved replies, and support settings.
• Managing webhook endpoints and deliveries, plus analytics.
• Reviewing Disaster Recovery incidents, recoveries, roll calls, allowances, readiness, failover settings, standbys, reminders, handover mail, and undo state.

Limitations and notes

Subscriby MCP server requires credentials with the abilities needed by the selected tools. OAuth represents the signed-in creator, while a personal access token is restricted to its granted abilities and team scope. Write operations can change workspace data, so clients should account for each tool’s declared read or change behavior before execution.

Rate limits, error formats, asynchronous jobs, security details, and versioning are documented separately by the project. The repository identifies the software license as MIT.