Coassemble for AI agents
Coassemble builds and delivers online training courses, letting a team create learning content and track who has completed it and when. 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 Coassemble.
Check a course's completion tracking
Check tracking data for a course to see who has finished it and who hasn't.
Look up enrolled users
Look up the users enrolled in a training program before sending a reminder.
Review client accounts
List client accounts before assigning a new course to the right group.
4 Coassemble actions, graded by risk.
Every Coassemble 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.
- coassemble.get_usersGet Users
- coassemble.get_clientsGet Clients
- coassemble.get_coursesGet Courses
- coassemble.get_trackingsGet Trackings
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Coassemble in three steps.
- 01Your users connect CoassembleThey add their Coassemble api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Coassemble through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('coassemble', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Coassemble connects.
Users add their Coassemble 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 Coassemble 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 Coassemble from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Coassemble and Arc0, answered.
Can I use Coassemble with Claude, ChatGPT or Cursor?
Yes. Connect Coassemble 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 Coassemble actions you allow.
How do users connect Coassemble?
Users add their Coassemble 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 Coassemble actions can my agent take?
4 in total: 4 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Coassemble?
Yes. Allow read actions and deny writes in the Coassemble policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Coassemble too?
Yes. The same Coassemble connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Coassemble into your agent.
Your users connect Coassemble 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