ProcessOn MCP Server
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance0/25
- Docs10/15
- License3/10
Tested npm @processon/mcp-server-processon-node 1.0.10 (license not stated; no source repo linked in package metadata). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 2 tools (no tool annotations). Real calls: No real function call could be made without credentials or a backing app (the server's only tools are setup/status checks). Calls need a PROCESSON_API_KEY. Core tools not tested: 70 cap.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): fail. No real function call could be made without credentials or a backing app (the server's only tools are setup/status checks). Calls need a PROCESSON_API_KEY. Evidence: local test run, Nov 18, 2026 UTC.
Transport (tested 2026-11-18 UTC): stdio
Token cost (estimate): approx. 113 tokens, cl100k estimate (2 tools, measured 2026-11-18 UTC, version 1.0.10). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 0 read, 1 write (state-changing), 1 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown
Auth: API key. Rate limit: unknown. Pricing unit: unknown.
check— unclassifiedcreateProcessOnMind— write (state-changing)
listing-flags calls_need_key or auth_kind
Score 63/100 · Tools 2 · Token cost approx. 113 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 1.0.10 · Package @processon/mcp-server-processon-node
Summary: ProcessOn MCP Server completed an MCP handshake without credentials and exposed 2 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 2
- Context cost
- approx. 113 tokens, cl100k estimate (2 tools, measured 2026-11-18 UTC, version 1.0.10; an estimate) ranking · add up your servers' context cost
- API key
- Connects without a key; tool calls need one
- Tested
- 2026-11-18 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @processon/mcp-server-processon-node --ignore-scripts (Node v24.22.1, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 2 tools listed in 15.8s. |
| maintenance | fail | 0 | No recent activity found. |
| docs | partial | 10 | README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package). |
| license | partial | 3 | License not machine-detected as OSI (no license found). |
Local-model readiness
Token cost (estimate): approx. 113 tokens, cl100k estimate for 2 tools · about 1% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-18 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 2 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-18 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
18ef312da2fd: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@processon/mcp-server-processon-node",
"version": "1.0.10",
"registry": "npm",
"status": "working",
"tested": "2026-11-18",
"tools_count": 2,
"deprecated": false,
"archived": null,
"tests": {
"install": [
"pass",
20,
"`npm install @processon/mcp-server-processon-node --ignore-scripts` (Node v24.22.1, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 2 tools listed in 15.8s."
],
"maintenance": [
"fail",
0,
"No recent activity found."
],
"docs": [
"partial",
10,
"README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"partial",
3,
"License not machine-detected as OSI (no license found)."
]
},
"testedAt": "2026-11-18T04:18:48.784Z"
}Install
npx -y @processon/mcp-server-processon-node
Pin the version we tested
npx -y --ignore-scripts @processon/mcp-server-processon-node@1.0.10
tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"mcp-server-processon-node": {
"command": "npx",
"args": [
"-y",
"@processon/mcp-server-processon-node@1.0.10"
]
}
}
}Tools listed
check, createProcessOnMind
Quick config
{
"mcpServers": {
"mcp-server-processon-node": {
"command": "npx",
"args": [
"-y",
"@processon/mcp-server-processon-node"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @processon/mcp-server-processon-node --ignore-scripts(Node v24.22.1). This is the exact command we ran on 2026-11-18 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (2 in our test).
{
"mcpServers": {
"mcp-server-processon-node": {
"command": "npx",
"args": [
"-y",
"@processon/mcp-server-processon-node"
]
}
}
}Test history
- 2026-11-18 UTC: New
Related: Troubleshooting: Protocol version mismatch (HTTP 400)
FAQ
Is ProcessOn MCP Server deprecated?
No. ProcessOn MCP Server was not deprecated or archived when we last tested it on 2026-11-18 UTC.
What replaces ProcessOn MCP Server?
Nothing; ProcessOn MCP Server is not deprecated as of 2026-11-18 UTC.
Does ProcessOn MCP Server need an API key?
It connects and lists 2 tools without a key, but its tool calls need one.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.