Connecting AI Assistants (MCP)

ProcessPlan includes a built-in MCP (Model Context Protocol) server. MCP is an open standard that lets AI assistants connect to your business tools. Once connected, your assistant can look up your process templates, check on running processes, review tasks and field values, and even complete tasks for you, all in plain conversation.

What your assistant can do

With a ProcessPlan connection, your AI assistant can:

List your process templates and inspect their steps and fields
List pending and completed process instances
Look up the tasks and field values of any process instance
See the tasks assigned to you
List the users and user groups in your account
Review your account’s audit log
Complete a pending task by submitting one of its responses

Everything the assistant sees is limited to your account, filtered by the same permissions as the user who signed it in or whose API token it uses. A task the assistant completes is recorded under the user’s name, like a response submitted in the app, and the audit log marks it as made through an AI assistant (see Changes made through an AI assistant).

The connection is for keeping up with work and reporting on it, not for redesigning it. An outside assistant cannot change how a process is built through this connection. To design or change a process in conversation, work with your AI Strategist inside ProcessPlan, where every change is shown to you and made only on your confirmation.

Set up the connection

There are two ways to connect. Use whichever your assistant offers.

Many assistants connect by having you sign in, with no token to copy.

In your assistant, add a custom connector (some assistants call it a remote MCP server) and give it this server URL: https://apius0.processplan.com/api/v4/mcp
Choose Connect. Your assistant opens the ProcessPlan sign-in page.
Sign in the way you normally do: with your password, with Google, or with your company’s single sign-on.
ProcessPlan shows which assistant is asking for access. Approve it to finish.

The assistant now works as you. It sees and does what you can, through the actions listed above.

Use an API token

If your assistant lets you set a header instead:

Create an API token in ProcessPlan: open your user profile and create a new API token. See API Authentication for details. Consider creating a dedicated user profile for AI integrations so its activity is easy to recognize.
Give your MCP client the server URL and your token:
- Server URL: https://apius0.processplan.com/api/v4/mcp
- Authentication: send your API token as a Bearer token (an Authorization: Bearer <your token> header) or in a header named tkn_id

Example configuration

Most MCP clients that take a token accept a JSON configuration like this, replacing your-token with your API token:

{
  "mcpServers": {
    "processplan": {
      "type": "http",
      "url": "https://apius0.processplan.com/api/v4/mcp",
      "headers": {
        "Authorization": "Bearer your-token"
      }
    }
  }
}

Security notes

A connection carries the identity and permissions of the user who signed in or who created the API token. The assistant can see and do exactly what that user can, nothing more.
A connection made by signing in works only for the actions listed above. It cannot be used anywhere else in ProcessPlan.
To end a connection made by signing in, remove it in your assistant. If you think an assistant was connected to your sign-in without your knowledge, contact ProcessPlan support to end it.
Treat an API token like a password. Anyone who has it can access your ProcessPlan data. You can delete the token from your user profile at any time to revoke access immediately.
Users with read-only access can browse data through MCP but cannot submit task responses.