Early bird discounts live! Claim your offer
MemberPass Logo

Connecting Cursor

Configure Cursor's MCP support to consume the MemberPass server.

Requirements

  • Cursor 0.46 or newer (MCP support GA).
  • A MemberPass personal access token with mcp:full.

Config

Cursor's MCP configuration lives at ~/.cursor/mcp.json on macOS / Linux and %APPDATA%\Cursor\mcp.json on Windows.

Add the server

Open the config file and merge:

{
  "mcpServers": {
    "memberpass": {
      "url": "https://mcp.memberpass.net",
      "headers": {
        "Authorization": "Bearer mpt_live_YOUR_TOKEN"
      }
    }
  }
}

Restart Cursor.

Verify

Open Composer (or chat) and ask:

Using the memberpass server, list my projects.

Cursor shows the tool invocation in its sidebar. You can approve each call individually or toggle "auto-approve for session" on the memberpass namespace.

Project-scoped versus user-scoped

Cursor also supports per-workspace .cursor/mcp.json. If you want the memberpass integration only active inside a specific repo, put the config there instead of the global location. Useful when you have a repo-specific MemberPass automation you want the AI agent to help with.

Troubleshooting

  • Tool list empty: check Cursor's "MCP" panel in the settings drawer for connection errors.
  • 403 on every call: token missing mcp:full.
  • 404 on specific tools: token missing the per-entity ability the tool enforces — see the tools reference.

How is this guide?

On this page

MemberPass is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request