Procesio

Provides tools to authenticate, list and view Procesio process templates, launch templates, and monitor workflow instances via an MCP client.

javascript

GitHub Stars

javascript

Language

2 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "serenichron-procesio-mcp-server": {
      "command": "node",
      "args": [
        "/path/to/procesio-mcp-server/build/index.js"
      ],
      "env": {
        "PROCESIO_REALM": "procesio01",
        "PROCESIO_API_KEY": "YOUR_API_KEY",
        "PROCESIO_PASSWORD": "your_procesio_password",
        "PROCESIO_USERNAME": "your_procesio_username",
        "PROCESIO_API_VALUE": "YOUR_API_VALUE",
        "PROCESIO_WEB_API_URL": "https://webapi.procesio.app/"
      }
    }
  }
}

You run a Procesio MCP Server to interact with the Procesio automation platform API. It lets language models and MCP clients list, view, and manage Procesio workflows and their running instances using API Key/Value authentication, enabling automated control and monitoring from your MCP workflow environment.

How to use

You connect to the MCP server from your MCP client and use the provided tools to manage Procesio workflows. Start by verifying authentication, then list available process templates, inspect details for a chosen template, launch an instance, and finally check the status of running or completed instances.

How to install

Prerequisites you need before installation:

Install Node.js LTS (recommended). You will run the build and start commands in the next steps.
Clone or obtain the MCP server package directory that contains the source files.
Install dependencies and build the server.
Run the server locally for testing and development.

Additional setup and configuration

Configure authentication and API endpoint access using environment variables. The server reads a set of variables needed to authenticate with Procesio and to locate the web API.

Create a local environment file or pass the variables through your MCP client settings to ensure the server receives all required values at startup.

Security and environment variables

The server uses API Key/Value authentication. Keep your API credentials secure and do not expose them in client-side code.

Examples and configuration snippets

PROCESIO_API_KEY='YOUR_API_KEY'
PROCESIO_API_VALUE='YOUR_API_VALUE'
PROCESIO_USERNAME='your_procesio_username' # Still needed for initial check, though not used for auth
PROCESIO_PASSWORD='your_procesio_password' # Still needed for initial check, though not used for auth
PROCESIO_WEB_API_URL='https://webapi.procesio.app/' # Or your specific instance URL
PROCESIO_REALM='procesio01' # Or your specific realm if different

{
  "mcpServers": {
    "procesio": {
      "command": "node",
      "args": [
        "/path/to/procesio-mcp-server/build/index.js"
      ],
      "env": {
        "PROCESIO_API_KEY": "YOUR_API_KEY",
        "PROCESIO_API_VALUE": "YOUR_API_VALUE",
        "PROCESIO_USERNAME": "your_procesio_username",
        "PROCESIO_PASSWORD": "your_procesio_password",
        "PROCESIO_WEB_API_URL": "https://webapi.procesio.app/",
        "PROCESIO_REALM": "procesio01"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Available tools

procesio_test_authentication

Tests the API Key/Value authentication by fetching current user details.

procesio_list_projects

Lists available Procesio process templates (workflows). Input supports pageNumber and pageItemCount.

procesio_get_project_details

Fetches detailed configuration for a specific process template (workflow) identified by projectId.

procesio_launch_project

Launches an instance of a specified process template. Accepts payload, runSynchronous, debugMode, secondsTimeOut, and connectionId.

procesio_get_instance_status

Retrieves the status of a running or completed process instance. Optional inputs include flowTemplateId and isArchived.

Built by

VeilStrat

AI signals for GTM teams