Algodocs for AI agents
AlgoDocs is an AI document processing platform that extracts data from business documents without templates. Back-office teams use it to automate data capture from paperwork. 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 Algodocs.
List document extractors
Review the data extractors configured on the account before routing a new document to one.
Check current user details
Look up the account and plan details tied to the current API credentials before running a new extraction job.
List document folders
Browse the folders where processed documents are organized before filing a new one.
3 Algodocs actions, graded by risk.
Every Algodocs action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- algodocs.get_meGet Current User
- algodocs.list_foldersList folders
- algodocs.list_extractorsList document data extractors
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.
Algodocs in three steps.
- 01Your users connect AlgodocsThey add their Algodocs 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 Algodocs through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('algodocs', { 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 Algodocs connects.
Users add their Algodocs 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 Algodocs 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 · Username and password
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Algodocs from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Algodocs and Arc0, answered.
Can I use Algodocs with Claude, ChatGPT or Cursor?
Yes. Connect Algodocs 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 Algodocs actions you allow.
How do users connect Algodocs?
Users add their Algodocs 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 Algodocs actions can my agent take?
3 in total: 3 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Algodocs?
Yes. Allow read actions and deny writes in the Algodocs policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Algodocs too?
Yes. The same Algodocs connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Algodocs into your agent.
Your users connect Algodocs 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