Process Street
Start workflow runs, complete tasks, update form fields and query data sets from your AI assistant. 32 tools, OAuth sign-in, available on all Process Street plans.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Process Street via MCP
https://mcp.process.stWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Process Street Tools & Capabilities (32)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- SAML SSO organizations cannot use it. Process Street's own documentation rules this out for now. For a product sold heavily into compliance and regulated operations teams, this excludes a large share of exactly the accounts most likely to want an audit-friendly connector.
- The OAuth scopes cannot narrow what it does. The protected-resource descriptor advertises only
openid,profile,emailandoffline_access. There is no application-level scope to decline at consent time, so a read-only connection is not something you can approve — authorisation comes from your Process Street permissions instead. - Deleting a data set record has no documented undo. Workflow runs can be restored by an Admin; individual data set records have no restore path in the documentation and no undelete tool.
- It manages runs, not workflow templates. The 32 tools act on workflow *runs*, tasks, form fields, approvals, assignments and data sets. Nothing in the list creates or edits a workflow template, so process design stays in the Process Street editor.
- Restricted API keys are Enterprise-only, and default to Admin. Process Street documents that every API key has an associated API key user created as an Admin by default, and that scoping it down to named resources is an Enterprise feature. On lower plans, a key issued for a bearer-token client carries full admin reach.
- No per-tool documentation exists publicly. Process Street's MCP page covers setup, clients, prerequisites and example prompts, but publishes no tool reference. We read 32 names from Anthropic's directory and no descriptions, parameters or safety annotations, because the endpoint requires OAuth.
- We did not exercise any tool. Our check was an anonymous protocol request that returned an OAuth challenge, plus a read of the server's own protected-resource descriptor. Everything above about tool behaviour comes from Process Street's documentation or the directory listing.
Frequently asked questions
Which Process Street plan do you need for the MCP server?
Every plan. Process Street's MCP documentation lists the feature as available on all plans, with no paid tier gate on the connector itself. The one plan-gated adjacent feature is restricted API keys, which its own help page limits to Enterprise. ChatGPT users need a Pro, Team, Business, Enterprise or Edu subscription on the ChatGPT side.
Does the Process Street MCP server work with SAML SSO?
No. Process Street's MCP documentation states plainly that if SAML SSO is enabled in your organization, the MCP server is not supported at the moment. This is the sharpest prerequisite on the page and it is an organization-level block, not a per-user setting, so SSO-enforced workspaces cannot connect until Process Street ships support.
What can the Process Street MCP server see and change in my account?
Only what your own account can. Process Street documents that Admins, Builders and Users can all use the MCP server, and that each can interact solely with resources they already have permission to reach. The connector inherits your existing role and folder, workflow and workflow run permissions rather than granting a separate level of access.
Can the Process Street MCP server permanently delete my data?
Workflow run deletion is recoverable; data set record deletion is not documented as recoverable. Process Street states that deleted workflow runs can be restored, and only by Admins. Its data set documentation describes no restore path for individual records, and the connector ships no undelete tool for them, so treat record deletion as final.
Do you need an admin account to connect Process Street to Claude?
Not for the standard OAuth connection. Process Street documents the Claude setup as signing in with your own credentials, and Admins, Builders and Users may all use the server. Admin rights matter for two adjacent things: generating an API key for clients without a one-click connector, and restoring any workflow run that was deleted.
How do you connect Process Street to an MCP client that has no built-in connector?
With a Process Street API key as a bearer token. Process Street documents adding https://mcp.process.st/ as a remote MCP server and sending an Authorization header carrying the key, with worked configuration examples for VS Code and Cursor. An administrator generates the key from the integrations page in the organization manager.
Sources
- Live auth posture check against
https://mcp.process.st— an anonymousinitializereturns - Using Process Street's MCP Server (HTTP 200, retrieved 2026-08-18; ~1,200 words, updated by the vendor 2026-08-07). Source for prerequisites, SAML SSO exclusion, plan availability, roles, client setup, bearer-token path and example prompts. · retrieved 2026-08-18
- Introducing Process Street's MCP Server (HTTP 200, retrieved 2026-08-18). Announcement post, dated 2026-01-27 by the vendor; source for "available on all plans" and the API-endpoints-as-tools framing. · retrieved 2026-08-18
- Managing User Permissions (HTTP 200, retrieved 2026-08-18). Source for the Admin, Builder, User and Guest role model. · retrieved 2026-08-18
- How To Delete Workflow Runs (HTTP 200, retrieved 2026-08-18). Source for who may delete a run and that only Admins may restore one. · retrieved 2026-08-18
- Data Sets (HTTP 200, retrieved 2026-08-18). Source for data set permissions and the absence of a documented record-level restore. · retrieved 2026-08-18
- Restricted API keys (HTTP 200, retrieved 2026-08-18). Source for Enterprise availability and the Admin-by-default API key user. · retrieved 2026-08-18
robots.txtforwww.process.st(HTTP 200, retrieved 2026-08-18). Disallows only/wp-admin/and carries noContent-Signaldirective, so fetching and synthesis are both unrestricted. The host also serves a help-centrellms.txtindex at , which is how the two MCP pages above were located. · retrieved 2026-08-18- Anthropic Connectors Directory entry, including the 32 tool names, permissions and tier (from the committed directory snapshot of 2026-08-16, re-read 2026-08-18) · retrieved 2026-08-16
- Process Street support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Process Street
- Tools
- 32
- Domain
- mcp.process.st
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.