procesio

MCP Server for interacting with the Procesio API

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio serenichron-procesio-mcp-server node /path/to/procesio-mcp-server/build/index.js \
  --env PROCESIO_REALM="procesio01" \
  --env PROCESIO_API_KEY="YOUR_API_KEY" \
  --env PROCESIO_PASSWORD="your_procesio_password" \
  --env PROCESIO_USERNAME="your_procesio_username" \
  --env PROCESIO_API_VALUE="YOUR_API_VALUE" \
  --env PROCESIO_WEB_API_URL="https://webapi.procesio.app/"

How to use

This MCP server provides a set of tools to interact with the Procesio automation platform API. It authenticates using an API Key/Value pair and exposes tools to test authentication, list available process templates (workflows), fetch details for a specific workflow, launch a workflow instance, and check the status of a running or completed instance. Use the procesio_test_authentication tool to verify your credentials, then explore procesio_list_projects to browse templates. Retrieve detailed information about a template with procesio_get_project_details and start an instance using procesio_launch_project. Finally, monitor progress with procesio_get_instance_status. Each tool accepts well-defined inputs, such as projectId for details/launch and instanceId for status, and supports optional parameters like pagination, payloads, timeouts, and headers as described in the tool documentation.

How to install

Prerequisites:

Node.js (LTS) installed on the host
npm installed
Access credentials for Procesio API (API Key/Value) and endpoint URL

Installation steps:

Clone the repository or download the source code for the Procesio MCP Server.
Install dependencies:

npm install

Build the server (if using a build step):

npm run build

Run the server locally (examples depend on your environment):

# Run directly with Node from the built entry point
node build/index.js

Alternatively, configure via MCP client settings (recommended): ensure the environment variables are provided to the server as shown in the mcp_config example, either through a .env file or the MCP client settings file (e.g., cline_mcp_settings.json) so that the server has access to PROCESIO_API_KEY, PROCESIO_API_VALUE, PROCESIO_USERNAME, PROCESIO_PASSWORD, PROCESIO_WEB_API_URL, and PROCESIO_REALM.

Additional notes

Environment variables are required for authentication and API endpoint configuration. Ensure PROCESIO_WEB_API_URL points to your Procesio instance, and PROCESIO_REALM matches the realm used for authentication. If you encounter authentication errors, double-check that the API key/value pair has the correct permissions. When running via MCP clients, prefer passing environment variables in the MCP settings file to guarantee they’re available to the Node process. The server listens on stdio for MCP requests; in some environments you may need to adapt the startup command to forward stdio correctly. If you plan to run multiple instances, ensure unique environment configurations per instance to avoid credential leakage between runs.

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.