Bring Membership Management
to Claude Desktop
Learn how to connect Memberful to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Memberful MCP Server?
Connect your Memberful account to any AI agent and take full control of your membership site orchestration and subscription efficiency through natural conversation. Memberful provides a powerful GraphQL platform for managing gated content and recurring revenue, and this integration allows you to retrieve member metadata, monitor active subscriptions, and oversee sales orders directly from your chat interface.
What you can do
- Member & Profile Orchestration — List all managed members and retrieve detailed profile metadata programmatically to ensure your audience database is always synchronized.
- Subscription Lifecycle Management — Access and monitor active subscriptions, expiration dates, and assigned plans directly from the AI interface to track recurring revenue health.
- Order & Financial Intelligence — List and oversee recent sales orders and retrieve detailed transaction metadata via natural language to maintain a clear overview of organizational liquidity.
- Plan & Discount Control — Retrieve master data for membership plans and available discounts using simple AI commands to facilitate better promotional alignment.
- Operational Monitoring — Track system responses and manage webhook metadata to ensure your automation workflows are always optimized.
How it works
1. Subscribe to this server
2. Enter your Memberful API Key and Site Name (subdomain) from your dashboard settings
3. Start managing your membership business from Claude, Cursor, or any MCP-compatible client
No more manual status checking in the dashboard for new subscribers. Your AI acts as a dedicated membership coordinator or operations assistant.
Who is this for?
- Publishers & Creators — quickly retrieve member summaries and monitor churn without switching apps.
- Operations Managers — automate the retrieval of subscription metadata and track plan distribution via natural conversation.
- Developers — integrate real-time membership data and site metadata directly within the chat.
Built-in capabilities (12)
Create a new member
Get site info
Get member details
Get order details
List active coupons
List member discounts
List member downloads
List all members
List recent orders
List subscription plans
List all subscriptions
List configured webhooks
Why Claude Desktop?
Claude Desktop is the definitive way to connect Memberful to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Memberful in Claude Desktop
Memberful and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Memberful to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Memberful in Claude Desktop
The Memberful MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Memberful for Claude Desktop
Every tool call from Claude Desktop to the Memberful MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the details for a specific member by their ID?
Yes! Use the get_member tool with the Member ID. Your agent will respond with complete metadata for the record, including email, plan details, and active subscription status in seconds.
How do I find my Memberful API Key?
Log in to your Memberful account, navigate to Settings > Custom Applications, and click Add New Custom Application to generate your unique secret token.
What is the site name?
The site name is the subdomain of your Memberful URL (e.g., if you log in at my-community.memberful.com, your site name is my-community).
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.