Membervault for AI agents
MemberVault is a relationship marketing platform for hosting courses, memberships, and digital products in one place for creators and course businesses. 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 Membervault.
Enroll a user in a course
Add a user to a course after their purchase is confirmed in another system.
Check a course's roster
List the courses available to confirm a user is enrolled in the right one, read-only.
Approve before deleting a user
Require approval before deleting a user, since it removes their course access entirely.
4 Membervault actions, graded by risk.
Every Membervault action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- membervault.get_coursesGet Courses
write
1Create and change things. Allow, or ask the user first.
- membervault.add_userAdd User to Course
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- membervault.delete_userDelete User
- membervault.remove_userRemove User from Course
Membervault in three steps.
- 01Your users connect MembervaultThey add their Membervault api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “add User to Course” can wait for the user, and “delete User” can be denied outright.
- 03Any agent can actYour agent calls Membervault through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('membervault', { read: 'allow', write: 'ask', // add_user destructive: 'deny', // delete_user }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Membervault connects.
Users add their Membervault 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 Membervault 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 Membervault from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Membervault and Arc0, answered.
Can I use Membervault with Claude, ChatGPT or Cursor?
Yes. Connect Membervault 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 Membervault actions you allow.
How do users connect Membervault?
Users add their Membervault 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 Membervault actions can my agent take?
4 in total: 1 read, 1 write and 2 destructive, such as “add User to Course”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Membervault?
Yes. Actions like “delete User” 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 Membervault too?
Yes. The same Membervault connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Membervault into your agent.
Your users connect Membervault once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan