leonardsellem/n8n-mcp-server

MCPcommunity
leonardsellemMITUpdated 1y agoGitHub

MCP server that provides tools and resources for interacting with n8n API

A Model Context Protocol (MCP) server that allows AI assistants to interact with n8n workflows through natural language. This project provides a Model Context Protocol (MCP) server that empowers AI assistants to seamlessly interact with n8n, a popular workflow automation tool. It acts as a bridge, enabling AI assistants to programmatically manage and control n8n workflows and executions using…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2kGitHub stars
295Forks
1y agoLast update
Package
Authorleonardsellem
LicenseMIT
Sourcegithub
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface11 tools · 4 privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedMay 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

11 tools · 4 privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

delete_executionprivilegedNo description published

This tool published no description. Forge does not invent one.

get_executionprivilegedNo description published

This tool published no description. Forge does not invent one.

list_executionsprivilegedNo description published

This tool published no description. Forge does not invent one.

run_webhookNo description published

This tool published no description. Forge does not invent one.

activate_workflowNo description published

This tool published no description. Forge does not invent one.

create_workflowNo description published

This tool published no description. Forge does not invent one.

deactivate_workflowNo description published

This tool published no description. Forge does not invent one.

delete_workflowprivilegedNo description published

This tool published no description. Forge does not invent one.

get_workflowNo description published

This tool published no description. Forge does not invent one.

list_workflowsNo description published

This tool published no description. Forge does not invent one.

update_workflowNo description published

This tool published no description. Forge does not invent one.

0 of 11 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

A Model Context Protocol (MCP) server that allows AI assistants to interact with n8n workflows through natural language. This project provides a Model Context Protocol (MCP) server that empowers AI assistants to seamlessly interact with n8n, a popular workflow automation tool. It acts as a bridge, enabling AI assistants to programmatically manage and control n8n workflows and executions using natural language commands. n8n instance with API access enabled You can also run the server using…

Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.