Process Street MCP Server

The Process Street MCP server is an official, provider-hosted Model Context Protocol implementation that lets AI assistants interact with your Process Street organization. It exposes most of the Process Street public API as tools, including operations on workflows, workflow runs, tasks, approvals, form fields, assignees, users, and data sets. The goal is to let agents run SOPs and checklists, query process data, and update workflow state through natural language instead of bespoke API integrations.

The server is hosted by Process Street and reached over a remote MCP endpoint. Authentication uses your Process Street login (the server inherits role-based permissions, so Admins, Builders, and Users can only act on resources they already have access to in the app). It is currently incompatible with organizations that have SAML SSO enabled. Supported clients include Claude (web and desktop via the Connectors UI), ChatGPT Pro/Team/Business/Enterprise/Edu, and Microsoft Copilot Studio agents.

This is the official Process Street offering. There are separate community implementations (for example, Composio's Process Street toolkit), but those typically expose a smaller subset of actions than the official MCP server, which mirrors the broader public API.

Tools

The Process Street MCP server is hosted by Process Street, so there is nothing to install or self-host. Connect a compatible MCP client to it and sign in with your Process Street credentials.

Prerequisites

• A Process Street account with appropriate role (Admin, Builder, or User)
• Organization is NOT using SAML SSO (currently unsupported)
• An MCP-compatible client (Claude, ChatGPT on a paid plan, or Microsoft Copilot Studio)

Claude (Connectors UI)

1. Sign in to Claude and Process Street in your browser.
2. In a Claude chat, click the + button.
3. Choose Connectors then Manage connectors.
4. Search for Process Street and click Connect.
5. Sign in to Process Street and authorize the connection.

ChatGPT (Pro / Team / Business / Enterprise / Edu)

1. Open Settings then Connectors.
2. Add a new connector and paste the Process Street MCP server URL (obtained from the Process Street app integrations page).
3. Authenticate with your Process Street credentials when prompted.
4. ChatGPT will prompt for confirmation before any data-modifying tool calls.

Microsoft Copilot Studio

1. Create or open an agent.
2. Add a Tool of type Model Context Protocol.
3. Search for Process Street MCP Server and create a connection, authenticating with your Process Street credentials.
4. Publish the agent and configure channels.

Generic remote MCP config (example shape)

{
  "mcpServers": {
    "process-street": {
      "url": "<Process Street MCP server URL from your account>",
      "transport": "http"
    }
  }
}

The exact server URL is shown in the Process Street app under the MCP integration; it is not published in the public help docs. Refer to the official help page for the latest connection details: https://www.process.st/help/docs/mcp-server/

• Kick off SOP runs from chat, for example creating a new onboarding workflow run for a hire and setting the due date and assignees automatically.
• Operational status checks across in-flight processes, like asking an agent which workflow runs are overdue or which approvals are waiting on a specific user.
• Bulk approve or reject approval tasks across multiple workflow runs after reviewing context an agent has summarized.
• Update form field values on a workflow run from data the agent gathered elsewhere (email, CRM, ticketing) without writing custom integration code.
• Query data sets with column filters to look up customer, vendor, or asset records during a conversation and feed them into other tools.

• "List all overdue workflow runs in our Customer Onboarding workflow and show who is assigned."
• "Create a new run of the 'Employee Offboarding' workflow for Jordan Lee, due next Friday, and assign it to the HR group."
• "Find all approval tasks assigned to me right now and approve any related to expense reports under $500."
• "Search the Vendors data set for rows where Status equals 'Pending Review' and summarize them."
• "Update the 'Account Owner' and 'Renewal Date' form fields on workflow run 12345 with the values from this email."

• Official, vendor-maintained MCP server, so capabilities track the Process Street public API closely.
• Broad coverage: workflows, runs, tasks, approvals, assignees, form fields, and data sets are all reachable.
• Respects existing Process Street role-based permissions, so agents cannot exceed the user's access.
• Works with mainstream clients including Claude, ChatGPT (paid plans), and Microsoft Copilot Studio.

• Not available to organizations using SAML SSO.
• ChatGPT support requires a paid plan (Pro, Team, Business, Enterprise, or Edu).
• Public documentation does not list the exact tool schemas or the server URL, you have to retrieve them from inside the app.

• Composio's Process Street toolkit, which exposes a smaller curated set of actions through Composio's MCP gateway.
• Zapier MCP with the Process Street Zapier integration, useful if you already orchestrate Process Street via Zaps.
• Direct use of the Process Street public API (https://developer.process.st) via a custom MCP server or HTTP tool if you need endpoints not yet exposed.