Memberstack for AI agents
Memberstack adds user authentication, payments, and member management to websites without requiring developers to write custom backend authentication code from scratch. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Memberstack.
Look up a member's plan
Check a member's current plan and status before answering an account question, read-only.
Update a member's profile
Update a member's custom fields after they change details in another system.
Approve before deleting a member
Require approval before deleting a member, since it removes their account and access entirely.
8 Memberstack actions, graded by risk.
Every Memberstack action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- memberstack.get_memberGet Member
- memberstack.list_plansList Plans
- memberstack.list_membersList Members
- memberstack.list_data_tablesList Data Tables
write
2Create and change things. Allow, or ask the user first.
- memberstack.create_memberCreate Member
- memberstack.update_memberUpdate Member
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- memberstack.delete_memberDelete Member
- memberstack.remove_free_planRemove Free Plan
Memberstack in three steps.
- 01Your users connect MemberstackThey add their Memberstack api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Member” can wait for the user, and “delete Member” can be denied outright.
- 03Any agent can actYour agent calls Memberstack through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('memberstack', { read: 'allow', write: 'ask', // create_member destructive: 'deny', // delete_member }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Memberstack connects.
Users add their Memberstack api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Memberstack connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Memberstack from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore security and identity apps.
Memberstack and Arc0, answered.
Can I use Memberstack with Claude, ChatGPT or Cursor?
Yes. Connect Memberstack to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Memberstack actions you allow.
How do users connect Memberstack?
Users add their Memberstack api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Memberstack actions can my agent take?
8 in total: 4 read, 2 write and 2 destructive, such as “create Member”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Memberstack?
Yes. Actions like “delete Member” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Memberstack too?
Yes. The same Memberstack connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Memberstack into your agent.
Your users connect Memberstack once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan