Edworking for AI agents
Edworking is a collaborative workspace combining project management, tasks, messaging, and time tracking for small teams, used by teams that want one tool instead of several. 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 Edworking.
Create a task in a project
Create a task under a project once a team lead assigns new work.
Log time against a task
Add a time entry to a task so hours worked are reflected in the project's tracking.
Confirm before deleting a task
Require approval before deleting a task, since it removes its history and logged time.
12 Edworking actions, graded by risk.
Every Edworking action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- edworking.get_taskGet Task
- edworking.list_tasksList Tasks
- edworking.list_statesList Project States
- edworking.list_foldersList Folders
- edworking.list_messagesList Messages
- edworking.list_projectsList Projects
write
4Create and change things. Allow, or ask the user first.
- edworking.create_taskCreate Task
- edworking.update_taskUpdate Task
- edworking.send_messageSend Message
- edworking.add_time_entryAdd Time Entry
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- edworking.delete_taskDelete Task
- edworking.remove_time_entryRemove Time Entry
Edworking in three steps.
- 01Your users connect EdworkingThey add their Edworking api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Task” can wait for the user, and “delete Task” can be denied outright.
- 03Any agent can actYour agent calls Edworking through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('edworking', { read: 'allow', write: 'ask', // create_task destructive: 'deny', // delete_task }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Edworking connects.
Users add their Edworking 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 Edworking 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 Edworking from any agent.
More project management apps.
Edworking and Arc0, answered.
Can I use Edworking with Claude, ChatGPT or Cursor?
Yes. Connect Edworking 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 Edworking actions you allow.
How do users connect Edworking?
Users add their Edworking 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 Edworking actions can my agent take?
12 in total: 6 read, 4 write and 2 destructive, such as “create Task”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Edworking?
Yes. Actions like “delete Task” 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 Edworking too?
Yes. The same Edworking connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Edworking into your agent.
Your users connect Edworking once, under your brand. Your agent gets 12 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan