MCP Server for AI Agents
Subscriby speaks the Model Context Protocol. Connect Claude Desktop, Cursor, ChatGPT Desktop, or VS Code to mcp.subscriby.net and drive your creator workflow in natural language.
Subscriby hosts a Model Context Protocol (MCP) server at https://mcp.subscriby.net. Any MCP-aware client can connect by signing in to Subscriby (OAuth 2.1) or with a personal access token, and drive the creator workflow through tool calls.
What you get
- 118 tools covering projects, plans, pass windows, subscribers, subscriptions, access codes, coupons, member support conversations, saved replies and inbox settings, payment methods, payments, transactions, resources, bot status and disconnection, teams, roles, groups, tokens, deep links, portal URLs, member moderation, message broadcasts, activity log, webhook endpoints and deliveries, analytics and reports (dashboard metrics, earnings, subscriber analytics, transaction breakdowns, plan performance), and async-job polling. Full catalog.
- 6 enum resources —
ability,error-code,payment-provider,platform-type,subscription-status,webhook-event. Agents load these for context before calling a tool. Reference. - No prompts are shipped — the entire surface is tools + resources.
- Fine-grained authorization. Every tool enforces its own ability (
project:view-any,project-subscription-plan:create, …), the same one its REST equivalent requires, so a leaked MCP token cannot act beyond the scopes you granted.
Connection details
- Endpoint:
https://mcp.subscriby.net - Transport: MCP streamable HTTP
- Auth: OAuth 2.1 — the client sends you to Subscriby to sign in and authorize, no token to copy — or
Authorization: Bearer sbt_live_...carrying the abilities of the tools you intend to call - Ability catalog:
subscriby://enums/abilityresource - Rate limit: 120 tool calls/min per token (
mcpbucket); unauthenticated probes capped at 5/min per IP
Signing in gives the client your own reach. An OAuth connection acts as
you on the team you are working in. When you want a narrower connection —
read-only, or one project — mint a personal access token with just the
*.view and *.view-any abilities and configure the client with it instead.
Which client?
Claude
claude.ai, Claude Desktop and Claude Code. Add the connector, sign in, done — recommended for long-running research tasks over your Subscriby data.
Cursor
Great if you're also editing config files alongside running MCP tools.
ChatGPT Desktop
Works identically with the Subscriby server.
VS Code + Claude extension
For workflows that need MCP inside an IDE without switching to Cursor.
Example prompts
Natural-language calls any MCP client can translate into tool invocations against the Subscriby surface:
- "How are my earnings last month split by payment provider?"
- "List my projects and tell me which one has the most active subscribers."
- "Which subscription plan in project Premium Trading earned the most revenue last month?"
- "Show me the five most recent failed payments across all my projects."
- "How many unredeemed access codes are outstanding on plan Elite Monthly?"
- "Audit the activity log for subscriber
usr_01H...— did anyone ban and unban them in the last 30 days?" - "Create a new project called 'Research Premium' and scaffold a monthly plan at $29."
- "Cancel
[email protected]'s subscription with reason 'user requested'."
Each tool's reference page includes more targeted examples.
Related
- Quickstart — two-minute setup.
- Authentication — OAuth connections and personal access tokens side by side.
- Tools reference — every tool with its required ability.
- Resources reference — the 6 enum resources.
- Async jobs — how long-running tools return a
job_idand let you poll. - Security — token scope, revocation, audit logging.
How is this guide?