Cults for AI agents
Cults is a digital marketplace for 3D printing models, where independent designers list and sell files for people to print at home. 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 Cults.
Query the marketplace catalog
Run a GraphQL query against Cults to look up a specific 3D model listing.
Check approved origins for embedding
Check which origins are approved before embedding a Cults listing on a site.
Share a new creation
Share a newly created model listing once a designer has uploaded it.
3 Cults actions, graded by risk.
Every Cults 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.
- cults.get_approved_originsGet Approved Origins
write
2Create and change things. Allow, or ask the user first.
- cults.graph_ql_postCults GraphQL POST
- cults.share_on_create_frShare on Create (FR)
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Cults in three steps.
- 01Your users connect CultsThey add their Cults api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “cults GraphQL POST” can wait for the user to approve.
- 03Any agent can actYour agent calls Cults through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('cults', { read: 'allow', write: 'ask', // graph_ql_post destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Cults connects.
Users add their Cults 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 Cults 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 Cults from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Cults and Arc0, answered.
Can I use Cults with Claude, ChatGPT or Cursor?
Yes. Connect Cults 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 Cults actions you allow.
How do users connect Cults?
Users add their Cults 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 Cults actions can my agent take?
3 in total: 1 read, 2 write and 0 destructive, such as “cults GraphQL POST”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Cults?
Yes. Allow read actions and deny writes in the Cults policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Cults too?
Yes. The same Cults connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Cults into your agent.
Your users connect Cults once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan