
Memberpass
net.memberpass由 memberpass.net 發布官方發布者v1.0.0更新於 Nov 2, 2026
MemberPass MCP — manage projects, plans, members, payments, and analytics for Telegram creators.
概覽
面向 Telegram 創作者的 Subscriby/MemberPass 遠端 MCP 伺服器,讓助理管理專案、方案、會員、付款、連接器與分析資料。
- 可以做什麼
- 管理專案、入口網站設計、方案、通行期間、訂閱與存取授權
- 管理會員、連結帳號、存取碼、付款方式與付款
- 操作連接器安裝、連接器市集、機器人、團隊、Webhook 與廣播訊息
- 處理優惠券、Smart Links、營收挽回、推薦計畫與合作夥伴計畫的分潤與撥款
- 讀取客服收件匣、知識庫項目、Copilot 額度、交易手續費與災難復原紀錄
- 查詢分析資料並匯出帳號持有的全部內容
- 適用情境
- 適合經營付費 Telegram 社群的創作者或團隊,希望助理檢視或操作其 Subscriby 工作區:核對會員與訂閱、查看營收與挽回數據,或不必在後台逐項點選就能設定連接器與方案。
- 執行需求
- 遠端端點 mcp.memberpass.net,使用 streamable HTTP。必須驗證:可用 OAuth 2.1 登入(PKCE S256),或在 Subscriby 應用程式依所選權限與團隊範圍建立個人存取權杖,透過 Authorization 標頭以 Bearer 方式送出。每個工具都要求特定權限。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Memberpass,將其新增到工作區。
- 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/net.memberpass%2Fmcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"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.
Connect from Cursor
Follow docs.subscriby.net/mcp/v1/connecting-cursor.
Connect from VS Code
Follow docs.subscriby.net/mcp/v1/connecting-vscode-claude.
Connect from ChatGPT Desktop
Follow docs.subscriby.net/mcp/v1/connecting-chatgpt-desktop.
Authentication
Two credentials work on the same endpoint:
- OAuth 2.1 — the client discovers the authorization server from the
401challenge, registers itself dynamically (RFC 7591) and sends you to Subscriby to sign in and authorize; PKCES256is 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 athttps://app.subscriby.net/settings/tokenswith 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
來源:README.md,提交 919e3f2
工具
0版本歷史
1- v1.0.0最新Sep 16, 2026
評分
已滿足適用檢查項的 60%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分