Pneumatic for AI agents
Pneumatic is a workflow management platform for designing reusable processes and coordinating tasks across a team. Operations teams use it to standardize recurring work. 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 Pneumatic.
Run a workflow template
Kick off a new workflow instance from a saved template for a recurring process.
Check a workflow's task status read-only
Look up a running workflow's tasks to see what step it is currently on.
Mark a task complete with approval
Set a task's completion only after the assigned person confirms the work is done.
10 Pneumatic actions, graded by risk.
Every Pneumatic action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- pneumatic.get_taskGet Task
- pneumatic.list_tasksList Tasks
- pneumatic.get_templateGet Template
- pneumatic.get_workflowGet Workflow
- pneumatic.list_datasetsList Datasets
- pneumatic.list_templatesList Templates
- pneumatic.list_workflowsList Workflows
write
3Create and change things. Allow, or ask the user first.
- pneumatic.run_templateRun Template
- pneumatic.save_datasetSave Dataset
- pneumatic.set_task_completionSet Task Completion
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Pneumatic in three steps.
- 01Your users connect PneumaticThey add their Pneumatic api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “run Template” can wait for the user to approve.
- 03Any agent can actYour agent calls Pneumatic through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('pneumatic', { read: 'allow', write: 'ask', // run_template destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Pneumatic connects.
Users add their Pneumatic 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 Pneumatic 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 Pneumatic from any agent.
More project management apps.
Pneumatic and Arc0, answered.
Can I use Pneumatic with Claude, ChatGPT or Cursor?
Yes. Connect Pneumatic 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 Pneumatic actions you allow.
How do users connect Pneumatic?
Users add their Pneumatic 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 Pneumatic actions can my agent take?
10 in total: 7 read, 3 write and 0 destructive, such as “run Template”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Pneumatic?
Yes. Allow read actions and deny writes in the Pneumatic policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Pneumatic too?
Yes. The same Pneumatic connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Pneumatic into your agent.
Your users connect Pneumatic once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan