Process Street for AI agents
Process Street lets teams create and run checklists, SOPs, and workflows to automate recurring processes. Operations teams use it to keep repeatable work consistent and trackable. 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 Process Street.
Create a new workflow run
Kick off a checklist run from a saved workflow template for a new task or onboarding.
Check workflows read-only
List available workflows to find the right template before starting a new run.
Complete a workflow run
Mark a workflow run complete once every required step has been checked off.
5 Process Street actions, graded by risk.
Every Process Street action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- process_street.list_workflowsList Workflows
- process_street.find_data_set_rowsFind Data Set Rows
write
3Create and change things. Allow, or ask the user first.
- process_street.create_workflow_runCreate Workflow Run
- process_street.complete_workflow_runComplete a workflow run
- process_street.undelete_workflow_runUndelete Workflow Run
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Process Street in three steps.
- 01Your users connect Process StreetThey add their Process Street api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Workflow Run” can wait for the user to approve.
- 03Any agent can actYour agent calls Process Street through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('process_street', { read: 'allow', write: 'ask', // create_workflow_run destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Process Street connects.
Users add their Process Street 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 Process Street 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 Process Street from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore project management apps.
Process Street and Arc0, answered.
Can I use Process Street with Claude, ChatGPT or Cursor?
Yes. Connect Process Street 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 Process Street actions you allow.
How do users connect Process Street?
Users add their Process Street 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 Process Street actions can my agent take?
5 in total: 2 read, 3 write and 0 destructive, such as “create Workflow Run”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Process Street?
Yes. Allow read actions and deny writes in the Process Street policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Process Street too?
Yes. The same Process Street connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Process Street into your agent.
Your users connect Process Street once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan