Moco for AI agents
MOCO is business management software combining project management, time tracking, and invoicing for service businesses that bill clients by the hour. 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 Moco.
Log a time activity
Create a time entry for work done on a project so it can be billed accurately.
Check a project's activities
List logged activities on a project to review time spent so far, a read-only check before invoicing.
Approve before deleting a company
Require approval before deleting a company record, since it affects linked deals and invoices.
218 Moco actions, graded by risk.
Every Moco action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
82Look things up. Allowed by default.
- moco.get_tagGet Tag
- moco.get_tagsGet Tags
- moco.get_unitGet Unit
- moco.get_userGet User
- moco.list_unitsList Units
- moco.get_commentGet Comment
- moco.get_companyGet Company
- moco.get_contactGet Contact
- moco.get_holidayGet Holiday
- moco.get_invoiceGet Invoice
- moco.get_profileGet Profile
- moco.get_receiptGet Receipt
- moco.get_cashflowGet Cashflow Report
- moco.get_presenceGet Presence
- moco.get_purchaseGet Purchase
- moco.get_receiptsGet Receipts
write
105Create and change things. Allow, or ask the user first.
- moco.create_tagCreate Tag
- moco.update_tagUpdate Tag
- moco.create_dealCreate Deal
- moco.create_unitCreate Unit
- moco.update_unitUpdate Unit
- moco.update_userUpdate User
- moco.create_offerCreate Offer
- moco.create_usersCreate User
- moco.create_commentCreate Comment
- moco.create_contactCreate Contact
- moco.create_holidayCreate Holiday
- moco.create_receiptCreate Receipt
- moco.update_commentUpdate Comment
- moco.update_companyUpdate Company
- moco.update_holidayUpdate Holiday
- moco.update_receiptUpdate Receipt
destructive
31Delete, cancel or archive. Ask first, or deny outright.
- moco.delete_tagDelete Tag
- moco.delete_userDelete User
- moco.delete_commentDelete Comment
- moco.delete_invoiceDelete Invoice
- moco.delete_projectDelete Project
- moco.delete_presenceDelete Presence
- moco.delete_purchaseDelete Purchase
- moco.delete_scheduleDelete Schedule
- moco.delete_taggingsDelete Taggings
- moco.delete_deal_categoryDelete Deal Category
- moco.delete_projects_tasksDelete Project Task
- moco.delete_contacts_peopleDelete Contact Person
- moco.delete_purchase_paymentDelete Purchase Payment
- moco.delete_invoices_paymentsDelete Invoice Payment
- moco.delete_projects_expensesDelete Project Expense
- moco.delete_users_employmentsDelete Employment
Moco in three steps.
- 01Your users connect MocoThey add their Moco api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Tag” can wait for the user, and “delete Tag” can be denied outright.
- 03Any agent can actYour agent calls Moco through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('moco', { read: 'allow', write: 'ask', // create_tag destructive: 'deny', // delete_tag }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Moco connects.
Users add their Moco 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 Moco 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 Moco from any agent.
Moco and Arc0, answered.
Can I use Moco with Claude, ChatGPT or Cursor?
Yes. Connect Moco 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 Moco actions you allow.
How do users connect Moco?
Users add their Moco 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 Moco actions can my agent take?
218 in total: 82 read, 105 write and 31 destructive, such as “create Tag”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Moco?
Yes. Actions like “delete Tag” 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 Moco too?
Yes. The same Moco connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Moco into your agent.
Your users connect Moco once, under your brand. Your agent gets 218 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan