MCP Server for AI Agents

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

• 161 tools covering your own account (who the token belongs to, its team, plan capabilities, connected accounts and alert routing), the Connectors Marketplace (every connector in its lane, what each can do and the form that connects it) and a project's connector installations (list and read them with their health; install, verify, configure, disconnect, and uninstall them after an impact preview), projects, plans, pass windows, subscriptions and their access grants, the hand-arranged perks still to deliver, the Disaster Recovery ledger (what is broken, what was done about it and whether it can still be undone, the re-admission roll call, the quota allowances and the readiness checklist) and its controls (failover settings, standbys and their mirror, the chat pickers the creator is sent, undo, reminders, the handover mail), subscribers and their connected accounts, 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, revenue composition, plan performance, analytics by connector), and async-job polling. Full catalog.
• 6 resources — the connectors/catalog directory and the ability, error-code, payment-provider, subscription-status and webhook-event enums. 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/ability resource
• Rate limit: 120 tool calls/min per token (mcp bucket); unauthenticated probes capped at 5/min per IP

Which client?

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_id and let you poll.
• Security — token scope, revocation, audit logging.