Memberstack MCP Server (Beta)

The Memberstack MCP (Model Context Protocol) Server connects AI tools like Claude directly to your Memberstack projects. This enables you to use natural language to interact with your members, subscription plans, data tables, and gated content.

Beta Notice: The Memberstack MCP Server is currently in beta. Features and functionality may change based on user feedback. Please report any issues or suggestions to our support team.

1) What Can You Do with the MCP Server?

• Manage Members: Create, update, search, and export member data in both LIVE and SANDBOX environments.
• Work with Data Tables: Build custom database structures, define fields, and manage records using natural language.
• Configure Plans: Set up pricing, access rules, and logic for your subscription tiers.
• Control Gated Content: Define which URLs are protected and which plans grant access.
• Search Knowledge: Perform semantic searches across Memberstack's documentation, guides, and resources.
• Switch Contexts: Seamlessly move between multiple apps and toggle between testing (SANDBOX) and production (LIVE) environments.

The MCP server provides approximately 68 specialized tools that understand the Memberstack data model, handle multi-project contexts, and respect environment boundaries.

2) Installation & Setup

Prerequisites

• An MCP-compatible client (e.g., Claude Code, Cursor, Codex, Claude Desktop, Cline).
• An active Memberstack account with dashboard access.
• Node.js installed on your machine to use the npx command.

Step 1: Configure Your Client

Find your AI client below and follow the instructions to register the Memberstack MCP Server.

Claude Code

Run this command in your terminal:

claude mcp add memberstack --scope user npx mcp-remote https://mcp.memberstack.com/mcp

The --scope user flag makes the server available globally across all your projects.

Codex

Run this command in your terminal:

codex mcp add memberstack -- npx mcp-remote https://mcp.memberstack.com/mcp

Cursor

Add the following to your Cursor MCP configuration file:

{
  "mcpServers": {
    "memberstack": {
      "command": "npx",
      "args": [ "mcp-remote", "https://mcp.memberstack.com/mcp" ]
    }
  }
}

Tip: Check Cursor's documentation for the exact location of the MCP configuration file.

Claude Desktop

Add the following to your Claude Desktop MCP configuration file:

{
  "mcpServers": {
    "memberstack": {
      "command": "npx",
      "args": [ "mcp-remote", "https://mcp.memberstack.com/mcp" ]
    }
  }
}

Tip: On macOS, the config file is typically located at ~/Library/Application Support/Claude/claude_desktop_config.json

Other Clients (Cline, Continue.dev, etc.)

JSON Configuration: Add this to your client's mcpServers configuration:

{
  "mcpServers": {
    "memberstack": {
      "command": "npx",
      "args": [ "mcp-remote", "https://mcp.memberstack.com/mcp" ]
    }
  }
}

YAML Configuration: If your client uses YAML (like some Continue.dev setups):

mcpServers:
  memberstack:
    command: npx
    args:
      - mcp-remote
      - https://mcp.memberstack.com/mcp

Step 2: Authenticate with Memberstack

1. After configuring your client, start a new conversation.
2. Your client will detect the new server and prompt you to authenticate. A browser window will open.
3. Log in with your Memberstack dashboard credentials to authorize the connection.

Security Note: The server uses OAuth 2.1 with PKCE. Your credentials are never shared with the AI client; authentication happens directly with Memberstack.

Step 3: Verify the Connection

Test your connection by asking your AI assistant:

"List my Memberstack apps"

The assistant should use the listApps tool and show you the Memberstack projects you have access to.

3) Core Concepts

Apps (Projects)

An App in Memberstack is a complete project or workspace. It contains its own members, plans, data tables, and settings. You must select an app context before performing most operations.

• Key Tools: listApps, switchApp, currentApp

Environments (LIVE vs. SANDBOX)

Each app has two isolated environments:

• SANDBOX: A free testing environment for development. Uses Stripe test data and does not affect your live members or charge real payments.
• LIVE: The production environment with real members and payments. Requires a paid Memberstack subscription for most features.

Important: Always verify your active environment to avoid accidentally modifying production data. Ask "What is my current environment?"

• Key Tools: getMemberstackEnvironment, switchMemberstackEnvironment

Authentication & Sessions

After you authenticate via OAuth, the MCP server maintains your session, including your active app and environment. To log out or switch Memberstack accounts, you must clear your local session token.

To log out and re-authenticate with Claude Desktop app:

1. Run the following command in your terminal:

rm -rf ~/.mcp-auth

1. Restart your client and start a new conversation.

4) Key Tool Groups Explained

The MCP server's ~68 tools are organized into logical groups. Here's an overview of what each group can do.

App & Environment Management

These tools allow you to navigate your Memberstack account. You can list all the projects (apps) you have access to, switch between them, and toggle between the SANDBOX and LIVE environments.

• Example Tools: listApps, switchApp, switchMemberstackEnvironment

Member Management

A comprehensive set of tools for managing your members. You can create, update, and delete members, manage their plan assignments, update their metadata, and handle bulk operations like imports and exports.

• Example Tools: createMemberEmailPassword, getMembers, updateMember, addFreePlan, exportMembers, deleteMember

Subscription Plan Management

Create and manage your subscription plans and pricing. These tools let you define plan details, create prices in Stripe, import existing Stripe products, and configure advanced plan logic like automatic upgrades or downgrades.

• Example Tools: createPlan, getPlans, createPrice (requires LIVE mode), importStripeProduct

Data Tables

Build and manage custom databases within Memberstack. You can create tables, define fields (text, number, boolean, etc.), and then create, read, update, and delete records in those tables. This is perfect for member profiles, directories, or custom content.

• Example Tools: createDataTable, createDataTableField, createDataRecord, getDataRecords

Gated Content

Control access to your website's content. These tools let you create content groups, protect specific URLs (including wildcards like /pro-content/*), and link subscription plans to grant access.

• Example Tools: createRestrictedUrlGroup, createRestrictedUrl, linkPlansToRestrictedUrlGroup

Knowledge Search

This single, powerful tool lets you perform a semantic search across the entire Memberstack knowledge base, including help articles, blog posts, and developer docs. It's your go-to for finding guides and troubleshooting steps.

• Key Tool: memberstackKnowledgeSearch

5) Common Workflows & Examples

Workflow 1: First-Time Setup

1. List apps: "List my Memberstack apps"
2. Select an app: "Switch to the 'My Awesome Site' app"
3. Check environment: "What is my current Memberstack environment?"
4. Switch if needed: "Switch to SANDBOX for testing"

This sequence uses listApps, switchApp, getMemberstackEnvironment, and switchMemberstackEnvironment to prepare your session.

Workflow 2: Creating a Member in a Test Environment

1. Confirm you're in SANDBOX: "Make sure I am in the SANDBOX environment"
2. Create a member: "Create a new member with email test@example.com and password 'SecurePassword123'"
3. Add a plan: "Find the 'Free Tier' plan and add it to test@example.com"
4. Verify creation: "Show me the details for the member with email test@example.com"

This uses switchMemberstackEnvironment, createMemberEmailPassword, addFreePlan, and getMembers.

Workflow 3: Setting Up a Gated Content Rule

1. Create a content group: "Create a gated content group called 'Pro Articles'"
2. Add a protected URL: "Add the URL '/pro/*' to the 'Pro Articles' group"
3. Link a plan: "Grant access to the 'Pro Articles' group for anyone on the 'Pro Membership' plan"
4. Verify: "Show me the configuration for the 'Pro Articles' content group"

This chain uses createRestrictedUrlGroup, createRestrictedUrl, linkRestrictedUrlsToRestrictedUrlGroup, and linkPlansToRestrictedUrlGroup.

6) Troubleshooting Common Issues

Problem: Memberstack tools don't appear in my client.

Solution: Fully quit and restart your client (Claude Desktop, VS Code, etc.). Ensure your JSON or YAML configuration file has no syntax errors and is saved in the correct directory for your specific client. If you used a CLI, verify the installation with the client's list command (e.g., claude mcp list).

Problem: I get "Unauthorized" or "Bearer token required" errors.

Solution: Your authentication session may have expired. To resolve this, run the command rm -rf ~/.mcp-auth in your terminal to clear the session. Afterward, restart your client and re-authenticate using the OAuth prompt. If the issue persists, try accessing the following URL: https://v2-api.memberstack.com (The page will be blank). Then, open the developer console and clear the cookies for the specified domain. As a precautionary measure, log out of your Memberstack dashboard and repeat the above process.

Problem: My terminal says "npx: command not found".

Solution: This means Node.js is not installed or not in your system's PATH. Install the latest LTS version of Node.js from nodejs.org, then restart your terminal and client.

Problem: I created a member but can't find them, or I'm seeing the wrong data.

Solution: You are likely in the wrong environment. Ask, "What Memberstack environment am I in?" and use switchMemberstackEnvironment to toggle between LIVE and SANDBOX as needed.

Problem: Tools fail with a "Requires Paid Subscription" error.

Solution: Certain tools that interact with Stripe (like createPrice or importStripeProduct) require a paid Memberstack subscription and must be run in the LIVE environment with Stripe connected. Check your subscription status in the Memberstack dashboard.

Problem: Operations fail with "No app context" or "App ID required".

Solution: You need to select which Memberstack project you are working on. Use listApps to see your available projects, then use switchApp with the desired App ID to set the context.

7) Complete Tool Reference (Quick List)

Here is a compact list of all available tools, organized by category.