@processon/mcp-server-processon-node
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BASE_URL | No | 自定义 API 地址（默认使用官方地址） | https://www.processon.com |
| PROCESSON_API_KEY | Yes | 你的 ProcessOn API 密钥（可在 www.processon.com 账户中心获取） |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| checkA | 查询用户当前配置apiKey，版本1.0.10 |
| createProcessOnMindB | 创建思维导图。根据markdown内容创建思维导图并返回ProcessOn文件链接。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools, 'check' and 'createProcessOnMind', serve clearly different purposes: one checks the API key configuration, the other creates a mind map from markdown. There is no overlap or ambiguity.
Naming style is inconsistent: 'check' is a simple lowercase verb, while 'createProcessOnMind' uses camelCase. With only two tools, the lack of a consistent pattern is noticeable.
Having only two tools seems too few for a server dedicated to ProcessOn functionality. A typical mind map service would include at least creation, listing, and perhaps deletion, making this feel incomplete and minimal.
The tool surface is severely incomplete for mind map management. Only creation is supported; there are no tools for listing, viewing, updating, or deleting mind maps, which limits the agent's ability to perform a full workflow.