procesio_test_authenticationLABSCO SUMMARY
Workflows triggered and watched from where the decision is made.
The gap in most automation platforms sits between deciding a process should run and going to the console to run it. Launch takes a payload and returns an instance ID, and the status call closes the loop without leaving the conversation.
What it is
A control surface for the Procesio automation platform: browse the process templates in your account, read one in detail, launch an instance of it with a payload, and check where that instance got to.
What you get
- The process templates listed, with page number and page size
- One template's full configuration, by its UUID
- An instance launched with an optional payload, synchronous or not, debug mode, a timeout in seconds and a connection ID
- Instance status for a running or completed run
- An authentication check that returns the current user's details
Requirements
A Procesio API key and its paired value in the environment, with the account username and password still read for the initial check. A .env file in the project root is the documented route.
Setup effort
Build from source
USE CASES
01
Finding the workflow you meant
Page through the templates and read the one that matches before launching anything.
02
Kicking off a process with real inputs
Launch the template with a payload rather than filling a form in the console.
03
Following a long run to its end
Poll the instance status instead of holding a synchronous call open.
04
Debugging a template that fails on launch
Launch it in debug mode, then read the instance status for where it stopped.
05
Confirming credentials before anything else
Run the authentication check and read the user it returns.
5 tools
Listed in project docs. Your client may show a different list.
procesio_list_projectsprocesio_get_project_detailsprocesio_launch_projectprocesio_get_instance_statusBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- PROCESIO_API_KEY in your environment
- PROCESIO_PASSWORD in your environment
- PROCESIO_API_VALUE in your environment
- PROCESIO_USERNAME in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/serenichron/procesio-mcp-server
cd procesio-mcp-server
npm install
npm run buildMCP Clients
Cline, Claude Desktop
JSON
{
"mcpServers": {
"procesio": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PROCESIO_MCP_SERVER>/build/index.js"
],
"env": {
"PROCESIO_API_KEY": "<YOUR_PROCESIO_API_KEY>",
"PROCESIO_API_VALUE": "<YOUR_PROCESIO_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": []
}
}
}
