Using Process Street’s MCP Server

OK: Other clients section
Process Street offers a Model Context Protocol (MCP) server, accessible via app integration, which allows AI assistants and other applications to access your workflows, workflow runs, tasks, users, and data sets from outside the Process Street platform.

This server provides a way to interact with your Process Street organization through various AI platforms and tools that support MCP.

Most MCP clients can connect automatically using Dynamic Client Registration (DCR), so no client ID or secret is required. Clients that don’t support DCR can still connect using a Process Street API key.

With this server, Process Street customers can:

1. Access Process Street data from compatible AI applications
2. Create and manage workflows runs & assign tasks
3. Generate reports and summaries based on Process Street data
4. Analyze Process Street data and get AI-powered suggestions

Example requests users could make from outside Process Street using the MCP:

1. “Create a new run of the Quarterly Access Review workflow and assign it to the compliance manager [[email protected]], if it’s not already been assigned to someone”
2. “Find the most recent Client Onboarding workflow runs and show me where there are bottlenecks from incomplete tasks”
3. “Search Data Set records for active vendors and, if they haven’t been reviewed in the past 6 months, mark them as Review”

The MCP server supports most Process Street API endpoints as tools.

The MCP server uses your Process Street login credentials to access it, including organizations with SAML SSO enabled.

Admins, Builders and Users can use the MCP server and can only interact with resources they have permissions to.

Requirements

A compatible MCP client, including:

• Claude (claude.ai)
• ChatGPT (Business, Enterprise, and Edu plans for full access; Pro plans are limited to read-only actions)
• Microsoft Copilot Studio
• VS Code
• Cursor
• Claude Code
• Gemini CLI
• Or any other application that has implemented an MCP client

How to set up the MCP

Claude

• Log in to Process Street (If you are part of more than one organization, be sure to switch to the one you’d like to connect the MCP with)
• Log in to Claude
• Click the + button in your chat
• Select Connectors, then select Manage connectors
• Select Browse Connectors, then type Process Street into the search box
• Click the + button to sign in with your Process Street credentials
• Authorize the app and open Claude to finish

ChatGPT

Note: ChatGPT Business, Enterprise, and Edu plans support full MCP access, including creating runs and updating tasks. Pro plans can connect with read-only access. On Business plans, only workspace admins and owners can add custom apps. On ChatGPT Enterprise and Edu, your ChatGPT admin may need to give you developer mode access first.

1. Log in to Process Street (if you are part of more than one organization, switch to the one you’d like to connect the MCP with)
2. In ChatGPT, go to Settings → Apps → Advanced settings and turn on Developer mode
3. Go to Settings → Apps → Create and enter the Process Street MCP server URL: https://mcp.process.st/
4. Set authentication to OAuth and leave the registration method on Dynamic Client Registration. You don’t need a client ID or secret.
5. Click Scan Tools, then sign in with your Process Street credentials and approve access
6. Click Create. Process Street appears under Enabled Apps, and its tools are available in your ChatGPT conversations.

Tip: ChatGPT usually asks you to confirm before running actions that modify data in Process Street (such as creating runs or updating tasks). Read-only actions like viewing workflows or pulling reports usually run without a confirmation prompt. Exact behavior depends on your ChatGPT app permissions.

Microsoft Copilot Studio

• Log in to Process Street (If you are part of more than one organization, be sure to switch to the one you’d like to connect the MCP with)
• Log in to Copilot Studio
• Create an Agent
• Add a tool, select Model Context Protocol and search for Process Street MCP Server
• Create a new connection
• Complete authentication
• Publish your Agent
• Connect the channels you’d like to connect the MCP with

Authorizing access

Each time you connect an MCP client (through Claude, ChatGPT, or Copilot Studio), Process Street displays an authorization screen. This screen shows the name of the application requesting access, the permissions (scopes) it needs, and the redirect URI, so you can confirm you recognize the application before granting access.

Click Approve to grant the application access to your Process Street data, or Cancel to deny the request. Canceling returns you to the connecting application without granting access.

Reviewing and disconnecting connected applications

After authorizing an application, you can review and manage all your connected applications from your personal settings.

1. Click your avatar or profile photo in the top-right corner, then select My Profile
2. Click the Apps tab

The Apps tab lists every OAuth-connected application across all organizations you belong to. Each row shows the application’s name, the permissions (scopes) it has, and when it was connected and last active.

To disconnect an application, click Disconnect next to it, then confirm in the dialog. Once disconnected, the application can no longer obtain new access tokens. Any access it already has through previously issued tokens may remain valid for up to one hour.

If no applications have been authorized yet, the tab shows an empty state.

Other clients

Process Street’s MCP server works with any application that supports the Model Context Protocol.

Connect with Dynamic Client Registration (recommended)

If your client supports OAuth with Dynamic Client Registration, point it to the MCP server URL and the client handles registration automatically:

1. Add https://mcp.process.st/ as a remote MCP server in your client
2. When prompted for a registration method, choose Dynamic Client Registration (usually the default)
3. Leave the client ID and client secret empty
4. Sign in with your Process Street credentials and approve access

This method works with VS Code, Cursor, Claude Code, Gemini CLI, and most other modern MCP clients.

Note: Some clients, such as Gemini Enterprise, don’t support DCR and require the API key method below instead.

Connect with an API key

For clients that don’t support OAuth or DCR, add Process Street as a remote MCP server and authenticate with a bearer token, using a Process Street API key as the token.

You’ll need two things:

• The MCP server URL: https://mcp.process.st/
• A Process Street API key. Admins can generate one from the integrations page in the organization manager. See Process Street API for details, and Restricted API keys if you want to limit what the key can do.

Then add an Authorization: Bearer YOUR_API_KEY header to your client’s MCP configuration. Two common examples follow. Treat your API key like a password.

VS Code

Tip: VS Code supports Dynamic Client Registration. Instead of the API key configuration below, add Process Street as a remote MCP server, choose Dynamic Client Registration when prompted, and leave the client ID and secret empty. VS Code handles the OAuth flow automatically.

If you prefer to connect with an API key, add the server to .vscode/mcp.json in your workspace, or open your user configuration with the MCP: Open User Configuration command. Using an input keeps the key out of the file: VS Code prompts for it once and stores it securely.

{
  "servers": {
    "process-street": {
      "type": "http",
      "url": "https://mcp.process.st/",
      "headers": {
        "Authorization": "Bearer ${input:ps-api-key}"
      }
    }
  },
  "inputs": [
    {
      "id": "ps-api-key",
      "type": "promptString",
      "description": "Process Street API key",
      "password": true
    }
  ]
}

Cursor

Tip: Cursor supports Dynamic Client Registration. Instead of the API key configuration below, add Process Street as a remote MCP server, choose Dynamic Client Registration when prompted, and leave the client ID and secret empty.

If you prefer to connect with an API key, add the server to ~/.cursor/mcp.json (available in every project) or .cursor/mcp.json (for a single project), then replace YOUR_API_KEY with your Process Street API key.

{
  "mcpServers": {
    "process-street": {
      "url": "https://mcp.process.st/",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

The same pattern, a remote MCP server with an Authorization: Bearer header, works for any other MCP client that supports remote servers but not Dynamic Client Registration.

If you’re using an MCP client that we don’t already support and need a hand, reach out to our support team.

• Learn the 5 stages of process building in our Getting started guide
• Watch helpful videos and webinars on our YouTube channel
• Learn about Process AI
• Collect info with Forms
• Organize data with Data Sets
• Document information and policies with Pages
• Get inspired by our Blog