# PROCESIO (pypi · procesio-cli)

Lets your own AI assistant build, run, validate and audit PROCESIO processes, forms and documents.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `procesio-mcp-0.1.6.mcpb`: 49/100, [markdown](https://verifymcp.io/servers/procesio-externals-procesio-cli/procesio-mcp.md), [page](https://verifymcp.io/servers/procesio-externals-procesio-cli/procesio-mcp)
- pypi · `procesio-cli`: 86/100 (this document), [markdown](https://verifymcp.io/servers/procesio-externals-procesio-cli/procesio-cli.md), [page](https://verifymcp.io/servers/procesio-externals-procesio-cli/procesio-cli)

## Channel facts

- Registry: `pypi`
- Package: `procesio-cli`
- Version: `0.1.6`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 3 of 30 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Procesio-Externals/procesio-cli).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1983 tokens (~94/item across 21 items; 21 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the PROCESIO MCP server?

PROCESIO runs locally as a PyPI package, launched with uvx procesio-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add procesio-externals-procesio-cli -- uvx procesio-cli
```

### Cursor

```json
{
  "mcpServers": {
    "procesio-externals-procesio-cli": {
      "command": "uvx",
      "args": [
        "procesio-cli"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "procesio-externals-procesio-cli": {
      "command": "uvx",
      "args": [
        "procesio-cli"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add procesio-externals-procesio-cli -- uvx procesio-cli
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "procesio-externals-procesio-cli": {
      "type": "local",
      "command": [
        "uvx",
        "procesio-cli"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add procesio-externals-procesio-cli --command uvx --arg procesio-cli
```

### Hermes

```yaml
mcp_servers:
  procesio-externals-procesio-cli:
    command: "uvx"
    args: ["procesio-cli"]
```

### Netclaw

```json
{
  "McpServers": {
    "procesio-externals-procesio-cli": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "procesio-cli"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add procesio-externals-procesio-cli -t stdio -c uvx -a procesio-cli
```

### Other

```json
{
  "mcpServers": {
    "procesio-externals-procesio-cli": {
      "command": "uvx",
      "args": [
        "procesio-cli"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 86, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 70, +1)

- [functional] Package version: 0.1.5 → 0.1.6

### 2026-10-31 (score 69, −14)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 83, +16)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 0.1.3 → 0.1.5
- [functional] Package version: 0.1.3 → 0.1.4

### 2026-10-27 (score 67)

First indexed and scored.

## MCP tools (21)

### `procesio_list_processes` (~121 tokens)

List PROCESIO processes

List the automation processes in a PROCESIO workspace, newest first. Use this to find the id of a process before running, editing or validating it.

Input parameters:

- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `page` (integer): 1-based page number.
- `page_size` (integer): Processes per page.
- `search` (string): Only processes whose name matches this text.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_create_process` (~117 tokens)

Create a PROCESIO process

Create a new automation process from a JSON definition of its steps and connections. Returns the new process id. Pass dry_run to see what would be built without creating anything.

Input parameters:

- `config` (string): The process definition, as a JSON object.
- `dry_run` (boolean): Report what would be created; create nothing.
- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_edit_process` (~144 tokens)

Edit a PROCESIO process

Change an existing process - add, retarget or reconfigure its steps. Pass dry_run first to see the diff. Removing steps additionally requires allow_remove, so a partial definition cannot silently delete work.

Input parameters:

- `allow_remove` (boolean): Permit this edit to delete steps.
- `config` (string): The changes, as a JSON object.
- `dry_run` (boolean): Report the diff; change nothing.
- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `id` (string, required): The process id.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_validate_process` (~111 tokens)

Validate a PROCESIO process

Check a process for errors without running it - unconnected steps, missing required inputs, broken references. Do this before running a process you just built. Validating is not the same as running: a process can validate and still fail at execution.

Input parameters:

- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `id` (string, required): The process id.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_run_process` (~158 tokens)

Run a PROCESIO process

Execute a process and return its run id. A process does real work - it can send mail, write to databases and call external systems - so this is never run unattended. Follow it with procesio_get_run_status and procesio_get_run_output.

Input parameters:

- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `id` (string, required): The process id.
- `payload` (string): Input values for the run, as a JSON object.
- `synchronous` (boolean): Wait for the run to finish instead of returning immediately.
- `timeout` (integer): Seconds to wait when synchronous.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_get_run_status` (~103 tokens)

Check a PROCESIO run

Report whether a run is still going, finished or failed, and which step it reached. Takes the run id returned by procesio_run_process.

Input parameters:

- `actions` (boolean): Include per-step detail.
- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `id` (string, required): The run id.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_get_run_output` (~88 tokens)

Read a PROCESIO run output

Return the values a finished run produced. Only meaningful once the run has completed - check with procesio_get_run_status first.

Input parameters:

- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `id` (string, required): The run id.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_tidy_process_layout` (~124 tokens)

Tidy a process canvas

Re-arrange a process's steps on the design canvas so it is readable. Changes only the visual layout, never what the process does. Worth running after building a process through the API, which places steps without arranging them.

Input parameters:

- `dry_run` (boolean): Report the new layout; change nothing.
- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `id` (string, required): The process id.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_list_forms` (~75 tokens)

List PROCESIO forms

List the forms in a workspace. A form is the screen a person fills in to start or feed a process.

Input parameters:

- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_get_form` (~80 tokens)

Read a PROCESIO form

Return a form's definition - its fields, their types and how they are laid out.

Input parameters:

- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `id` (string, required): The form id.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_create_form` (~107 tokens)

Create a PROCESIO form

Create a form from a JSON definition. Returns the new form id. Add fields afterwards with procesio_add_form_field.

Input parameters:

- `config` (string): The form definition, as a JSON object.
- `dry_run` (boolean): Report what would be created; create nothing.
- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_add_form_field` (~121 tokens)

Add fields to a PROCESIO form

Add one or more input fields to an existing form.

Input parameters:

- `dry_run` (boolean): Report what would be added; add nothing.
- `elements` (string): The fields to add, as a JSON array.
- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `id` (string, required): The form id.
- `parent` (string): Id of the container to add them into.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_build_connector` (~122 tokens)

Build a PROCESIO connector from API docs

Start building a custom PROCESIO connector from an API's documentation. Give it the docs URL and what you need the connector to do; it reads the docs, asks what it still needs, and generates a connector package. Returns a build id - follow it with procesio_get_connector_build.

Input parameters:

- `api_docs_text` (string): The documentation itself, if there is no public URL.
- `api_url` (string): URL of the API documentation to read.
- `user_requirements` (string): What the connector needs to do, in plain language.

### `procesio_list_connector_builds` (~44 tokens)

List connector builds

List connector builds and their current stage.

Input parameters:

- `page` (integer): 1-based page number.
- `status` (string): Only builds in this stage.

### `procesio_get_connector_build` (~44 tokens)

Check a connector build

Report a build's stage, what it is waiting on, and whether a connector package is ready to download.

Input parameters:

- `build_id` (string, required): The build id.

### `procesio_download_connector` (~56 tokens)

Download a built connector

Save a finished build's connector package to a local file, ready to install with procesio_install_connector.

Input parameters:

- `build_id` (string, required): The build id.
- `out` (string, required): Local path to write the package to.

### `procesio_install_connector` (~100 tokens)

Install a connector into PROCESIO

Install a connector package into a workspace, after which its operations appear as steps you can use when building a process.

Input parameters:

- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `file` (string, required): Path to the connector package.
- `name` (string): Name to show in the designer.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_list_connectors` (~71 tokens)

List installed connectors

List the connectors installed in a workspace - the extra step types available when building a process.

Input parameters:

- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_list_workspaces` (~75 tokens)

List PROCESIO workspaces

List the workspaces this account can reach. A workspace holds its own processes, forms, connectors and credentials.

Input parameters:

- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

### `procesio_list_environments` (~27 tokens)

List PROCESIO environments

List the configured environments, so a call can be pointed at the right one.

### `procesio_test_credential` (~95 tokens)

Test a PROCESIO credential

Check that a stored credential can still reach the system it belongs to. Answers whether a connection is working without running a whole process.

Input parameters:

- `config` (string): The credential to test, as a JSON object.
- `environment` (string): Named environment, e.g. Internal-QA. Omit for the default.
- `workspace_id` (string): Workspace to act in. Omit to use the default workspace.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/procesio-externals-procesio-cli/procesio-cli#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 67
- 2026-10-27: 67

## Common questions

### What is the PROCESIO MCP server?

PROCESIO is an MCP server listed in the public MCP registry as io.github.Procesio-Externals/procesio-cli. Lets your own AI assistant build, run, validate and audit PROCESIO processes, forms and documents. This page covers its PyPI package (procesio-cli).

### Is the PROCESIO MCP server safe to use?

PROCESIO scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the PROCESIO MCP server expose?

PROCESIO exposes 21 tools: procesio_list_processes, procesio_create_process, procesio_edit_process, procesio_validate_process, procesio_run_process, and 16 more. Their descriptions and schemas cost roughly 1,983 tokens of context every time the server is loaded.

### Is the PROCESIO MCP server still maintained?

PROCESIO is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the PROCESIO MCP server under?

PROCESIO declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the PROCESIO MCP server?

VerifyMCP ran 16 checks on PROCESIO, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/procesio-cli/
- Socket report: https://socket.dev/pypi/package/procesio-cli
- Repository: https://github.com/Procesio-Externals/procesio-cli
- Changelog RSS feed: https://verifymcp.io/servers/procesio-externals-procesio-cli/procesio-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/procesio-externals-procesio-cli/procesio-cli/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/procesio-externals-procesio-cli/procesio-cli.json
- HTML version of this page: https://verifymcp.io/servers/procesio-externals-procesio-cli/procesio-cli