Memberpass

net.memberpassPublished by memberpass.netOfficial publisherv1.0.0Updated Nov 2, 2026

MemberPass MCP — manage projects, plans, members, payments, and analytics for Telegram creators.

VerifiedStreamable HTTPWeb executableFinance Communication & Collaboration Business & Commerce

Server details

Identifier: net.memberpass/mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to memberpass.net, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/net.memberpass%2Fmcp.svg)](https://sourceweft.com/mcp/net.memberpass%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote MCP server for Subscriby/MemberPass that lets an assistant manage projects, plans, members, payments, connectors and analytics for Telegram creators.

What you can do: Manage projects, portal design, plans, pass windows, subscriptions and access grants
Administer members, connected accounts, access codes, payment methods and payments
Run connector installations, the Connectors Marketplace, bots, teams, webhooks and broadcasts
Handle coupons, Smart Links, Revenue Recovery, the Referral Program and Partner Program payouts
Read the support inbox, Knowledge entries, Copilot Credits, Transaction Fees and Disaster Recovery records
Query analytics and export everything the account holds
When to use it: Useful when a creator or team running a paid Telegram community wants an assistant to inspect or operate their Subscriby workspace: checking members and subscriptions, reviewing revenue and recovery figures, or configuring connectors and plans without clicking through the dashboard.
Requirements: A remote endpoint at mcp.memberpass.net over streamable HTTP. Authentication is required: either OAuth 2.1 sign-in (PKCE S256) or a personal access token sent as an Authorization bearer header, minted in the Subscriby app with chosen abilities and team scope. Each tool enforces a specific ability.

Before you install

The token grants account-wide access as you on the team you are working in, so scope its abilities narrowly. Many tools change data, including installing or uninstalling connectors, publishing portal changes, payouts, buying Copilot Credit packs through Stripe Checkout and auto top-up, and letting Copilot answer members; the README says each tool declares whether it reads or changes data, so confirm before destructive calls. The export tool returns everything the account holds.

Installation

In SourceWeft

Open Memberpass in the dashboard and add it to a workspace.
Connect Authorization token credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.memberpass%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "memberpass": {
      "type": "http",
      "url": "https://mcp.memberpass.net/",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Subscriby MCP Server

Connect Claude, Cursor, VS Code and other MCP clients to your Subscriby workspace.

What is Subscriby?

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.

What this MCP server exposes

217 tools across your own account (who the token belongs to, its team, plan capabilities, connected accounts and alert routing, the notification centre, an export of everything it holds, and its standing in the Partner Program: the code and links, the commission ladder, the referrals, the ledger and the payouts, with the payout rail written but never read back, and its Transaction Fees ledger: every fee Subscriby charged it, line by line and added up per month, with the invoice that billed each, and its Copilot Credits, the prepaid pool that pays for Subscriby Copilot past the monthly free allowance: the balance split into free and paid, the statement, a pack to buy on a Stripe Checkout page and the auto top-up and cap), 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 and their portal design (the look of the portal page: read the published document and the draft, change its keys, publish or discard), 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, Smart Links (a tracked address per channel with its three addresses to share and the funnel behind it), Revenue Recovery (the grace window with its ladder in words, the cancellation screen's offers and the feedback it gathered, the recovery sequences with their steps and the passages members made through them, the checkout ledger, and the figures the dashboard card shows), the Referral Program (the programme, its affiliates, their referrals, the reward ledger and the payouts the creator records), subscriptions, members and their connected accounts, the support inbox (conversations, saved replies, settings with the two switches that let Subscriby Copilot answer members), Knowledge (what a project has taught Subscriby Copilot: questions with their answers and documents sent as text, each marked for members or for the team alone), 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.

Connect from Claude

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.

Authentication

Two credentials work on the same endpoint:

OAuth 2.1 — the client discovers the authorization server from the 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.
Personal access token — 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.

Required token abilities

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.

Rate limits

See docs.subscriby.net/api/v1/rate-limiting.

Error envelope

See docs.subscriby.net/api/v1/errors.

Async jobs

See docs.subscriby.net/mcp/v1/async-jobs.

Security

See SECURITY.md.

Status & versioning

See CHANGELOG.md. The version field in server.json is the canonical version published to the MCP Registry.

License

MIT.

Support

[email protected]

Source: README.md at commit 919e3f2

Tools

This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts