pingLABSCO SUMMARY
Node lookup and workflow syntax checks, without leaving the editor.
The catalogue search earns its place: n8n has a lot of nodes and their names do not always say what they do, so keyword search across descriptions and use cases beats scrolling the palette. Validation is syntax-level — it catches a malformed workflow file, not a workflow that runs but is wrong.
What it is
A Go server for n8n work: it checks a workflow file's syntax, searches the node catalogue by keyword, and looks up community workflow templates.
What you get
- validate_workflow checks the syntax of an n8n workflow held in a JSON file
- search_n8n_nodes finds n8n nodes by keyword
- search_workflow searches community n8n workflow templates
- ping confirms the server is reachable
- Tool and parameter descriptions come back in the language you pick: Korean, English, Japanese, Vietnamese, Traditional Chinese or Thai
- A standalone build bakes the node data into the binary, so it runs with no external data files
- Search weighting across name, overview, use case and operation is adjustable at launch
Requirements
Go to build, or a prebuilt binary for your platform. It runs as a local process with no account or key, and the standalone build needs no data directory beside it.
Setup effort
Build from source — git clone https://github.com/n8nKOR/n8n-workflow-mcp.git
USE CASES
01
Finding the node that does the thing you need
Search the catalogue by what you are trying to do rather than by the node's product name.
02
Starting from someone else's workflow
Look through community templates for one close to your problem before building from an empty canvas.
03
Checking a workflow file before you import it
Validate the JSON against n8n's expectations so a broken import fails here rather than in the editor.
04
Confirming the server is wired up
One call tells you whether the client is really talking to it before you debug anything else.
4 tools
Listed in project docs. Your client may show a different list.
validate_workflowsearch_n8n_nodessearch_workflowBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- go on PATH
- Go 1.23
Where it runs
All 4 documented setups 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/n8nKOR/n8n-workflow-mcp.git
cd n8n-workflow-mcp
make build-standaloneMCP Clients
Claude Code — macOS, Cursor — macOS
JSON
{
"mcpServers": {
"n8n-kor-workflow": {
"command": "/Users/<YOUR_USERNAME>/<YOUR_CLONE_PATH>/build/n8n-mcp-server",
"args": [
"--standalone",
"--lang",
"ko"
]
}
}
}/Users/<YOUR_USERNAME>/<YOUR_CLONE_PATH> is the full path of your n8n-workflow-mcp clone. build/n8n-mcp-server is the program make build-standalone creates there. --lang ko makes the tool and parameter descriptions Korean (the default); change "ko" to "en" for English, or jp, vn, tw, th.
Claude Code — Windows, Cursor — Windows
JSON
{
"mcpServers": {
"n8n-kor-workflow": {
"command": "<YOUR_PATH_TO_N8N_WORKFLOW_MCP>\\build\\n8n-mcp-server.exe",
"args": [
"--standalone",
"--lang",
"ko"
]
}
}
}<YOUR_PATH_TO_N8N_WORKFLOW_MCP> is the full path of your clone (inside JSON, write each backslash twice, as shown). The project builds the Windows program with make build-standalone-windows. --lang ko makes the tool and parameter descriptions Korean (the default); change "ko" to "en" for English, or jp, vn, tw, th.
