n8n Workflow Automation MCP. Debug failures and audit access without touching a dashboard.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
n8n MCP Server gives your AI agent full control over node-based workflow automation. You can audit active workflows, pull detailed execution logs for debugging failures, and check system credentials—all without logging into the n8n dashboard.
It's diagnostic power for complex business processes.
What your AI agents can do
Get execution details
Retrieves the full, detailed trace logs for one specific workflow run.
Get workflow details
Gets the complete logic map and configuration details for a specified workflow.
List instance users
Lists all team members who have access to the n8n automation instance.
List all workflows, check their organizational tags, or retrieve detailed logic maps for a single process.
Get metadata on saved API credentials and list every user who has access to the n8n instance.
List recent runs, check success/failure status, and retrieve full trace logs for immediate debugging.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
n8n (AI Workflow Automation) MCP Server: 7 Tools for Diagnostics
Use these seven tools to inventory workflows, check user access, monitor executions, and pull detailed diagnostic logs from your n8n instance.
019d75daget execution details
Retrieves the full, detailed trace logs for one specific workflow run.
019d75daget workflow details
Gets the complete logic map and configuration details for a specified workflow.
019d75dalist instance users
Lists all team members who have access to the n8n automation instance.
019d75dalist stored credentials
Shows metadata for every saved API credential in the system, verifying types and IDs.
019d75dalist workflow executions
Lists a record of recent workflow runs, including their status (success/failure).
019d75dalist workflow tags
Retrieves the organizational categories used to group and sort workflows.
019d75dalist workflows
Provides an inventory list of all active automation workflows in the instance.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with n8n (AI Workflow Automation), then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
n8n MCP Server gives your AI agent full control over node-based workflow automation. You'll use this server to audit active workflows, pull detailed execution logs for debugging failures, and check system credentials—all without ever having to log into the n8n dashboard yourself. It’s diagnostic power built specifically for complex business processes.
Inventory Workflows
To get a handle on your automation setup, you can use list_workflows to pull an inventory list of every active workflow in the instance. You'll also find list_workflow_tags, which retrieves the organizational categories used to group and sort those workflows. Need more detail? Run get_workflow_details for a specific workflow ID; that gives you the complete logic map and configuration details for that single process.
Monitor Execution Health
When something breaks, you don't wanna dig through logs manually. You can start by running list_workflow_executions, which lists recent workflow runs and shows their status—success or failure. If a run failed, use get_execution_details to retrieve the full, detailed trace logs for that specific attempt. This gets you straight to the error code without any guesswork.
Audit Credentials and Users
You need to know who's running what and if the keys are safe. Use list_instance_users to list every team member who has access to the n8n automation instance. For system security, run list_stored_credentials; this shows you metadata for every saved API credential in the system, letting you verify types and IDs without ever seeing a literal secret token.
You connect your AI client to this server, and it gives your agent direct, programmatic access to the core diagnostics and metadata of your entire automation setup. You don't have to navigate complex dashboards; you just ask for what you need. The system executes the necessary tool calls and hands you a clean JSON output ready for review.
How n8n Workflow Automation MCP Works
- 1 Subscribe to the server and provide your n8n Base URL and API Key.
- 2 Tell your agent what you need (e.g., 'Show me recent failures in the lead ingestion workflow').
- 3 The agent runs the necessary tool calls, fetching the data and presenting it to you directly.
The bottom line is: You get a conversational interface to complex machine diagnostics, bypassing manual dashboard navigation entirely.
Who Is n8n Workflow Automation MCP For?
This setup is for Ops Engineers who are tired of clicking through dashboards at 2 am. If you manage workflows or need to audit API access across multiple nodes, this gives you the direct command line visibility you need without leaving your terminal.
Uses get_workflow_details and list_workflows to verify complex node-based designs before deployment.
Runs diagnostics by using list_workflow_executions followed by get_execution_details to track down why a batch job failed last night.
Checks access boundaries by calling list_instance_users and reviewing credential metadata via list_stored_credentials.
What Changes When You Connect
- Stop guessing why workflows fail. Instead of digging through logs manually, use
get_execution_detailsto pull the absolute trace log for any specific run. You see exactly where it broke down. - Audit system permissions instantly. Don't rely on memory when checking who can access what. Use
list_instance_usersandlist_stored_credentialsto get a clear, auditable list of users and API keys. - Know your whole process map. Want to see the full logic of a workflow? Call
get_workflow_details. You get the node-by-node JSON logic map right in your chat window. - Track automation health at a glance. Use
list_workflow_executionsto check recent runs. It's faster than clicking through the 'Executions' tab just to see if anything failed. - Keep things organized. Need to filter workflows by project? Call
list_workflow_tagsand then use that list in conjunction withlist_workflowsfor precise filtering.
Real-World Use Cases
Debugging a broken webhook.
The lead sync broke overnight. Instead of navigating to the 'Executions' page, you ask your agent to run list_workflow_executions for the 'Lead Sync' workflow. The results point to an ID: 901. You then call get_execution_details using that ID and immediately see the exact API error code on the failed node.
Checking access compliance.
Security mandates a review of all active credentials. You run list_stored_credentials. The agent shows you metadata for every credential, confirming if they're expired or if they are linked to sensitive services like 'CRM-Prod'.
Understanding legacy logic.
A colleague points out a workflow called 'Old Report Gen.' You use list_workflows to confirm its existence, then call get_workflow_details. The agent spits out the entire JSON structure, letting you understand the complex data flow without ever opening the n8n UI.
Onboarding a new team member.
You need to verify who has access. You ask your agent to run list_instance_users. It gives you a list of everyone, their roles, and confirms that the new hire's account is active and mapped correctly.
The Tradeoffs
Assuming visibility means access
You see 'Slack-Bot-Cred' listed in a general API console. You assume it’s safe to use because you can see its ID, but you don't know if the user who set it up actually left or changed roles.
→
Always check two things: first, run list_stored_credentials for the name. Second, cross-reference that credential owner against a call to list_instance_users to confirm their current status.
Searching by function only
You know 'the payroll workflow' exists, but you don't remember the exact name or ID. You waste time clicking through dozens of workflows in the dashboard.
→
Start with list_workflows. This gives you a clean inventory list, allowing your agent to find the correct workflow title for you.
Ignoring failure context
The process failed. You only know the general time frame and check the status of the main workflow without knowing which node actually threw the error.
→
First, call list_workflow_executions to get a list of recent failures. Then, take the ID from that failure and pass it to get_execution_details. This narrows the focus instantly.
When It Fits, When It Doesn't
Use this server if your primary pain is diagnosing complex automation logic or auditing internal system access. If you need to know what happened (logs, executions, users), these tools give you direct API calls.
Don't use it if you just want a simple status check on one item; in that case, a basic read-only API call might suffice. Also, don't use it for modifying workflows—it’s purely diagnostic and informational. If your requirement is policy enforcement (i.e., 'Does User X have permission to run Workflow Y?'), this set of tools confirms what exists, but you need an external Policy Decision Point layer above these functions to confirm who can do what.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by n8n. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 7 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Debugging a failed node shouldn't require 5 different tabs and copy-pasting IDs.
Today, when your automated process fails—and it will fail—you have to jump into the n8n dashboard. You find the workflow ID, then you click 'Executions,' hoping to spot the failure time. Then you select that run and dig through logs until you hit a wall of text, trying to pinpoint which node threw the error.
With this MCP server, you just ask your agent: 'What went wrong with my billing sync?' The agent runs `list_workflow_executions`, finds the ID for the failure, and instantly executes `get_execution_details`. You get the full trace log—the precise line number and error code—without opening a single tab.
n8n (AI Workflow Automation) MCP Server: Get immediate visibility into credentials.
Before, auditing required manually navigating to the 'Credentials' section. You had to scroll through lists and remember which credential belonged to which service—a tedious process prone to human error.
Now, you simply call `list_stored_credentials` via your agent. It returns a structured list of every saved key and its type. You validate system access quickly, knowing exactly what's stored without needing manual clicks.
Common Questions About n8n Workflow Automation MCP
How do I check if my n8n workflow is active using the list_workflows tool? +
The list_workflows tool provides an inventory of all workflows. You can filter this output based on status or use the retrieved details with get_workflow_details to confirm its current activity settings.
What if I want to see a failure that happened last month? Can get_execution_details handle old logs? +
list_workflow_executions shows recent runs. For older history, you'll need to ensure your n8n instance retains those historical records and then use the appropriate ID with get_execution_details.
Does list_instance_users tell me what roles people have? +
Yes. The list_instance_users tool returns metadata about provisioned team users, including their assigned roles within the n8n infrastructure for access control verification.
Can I use list_workflow_tags to group related workflows? +
Absolutely. Calling list_workflow_tags gives you all available organizational categories. You can then reference these tags when asking the agent to filter results from list_workflows.
When I use list_stored_credentials, how do I verify the type of saved credential? +
The tool lists metadata mapping credentials to their system types. It verifies the necessary ID and type without exposing any literal secure tokens, keeping your data safe while you audit.
Does get_execution_details provide enough information for deep troubleshooting of a failure? +
Yes. This tool retrieves absolute trace logs for a specific execution ID. This lets you pinpoint the exact node and process that failed, making debugging quick and precise.
How do I get a structural view of a workflow using get_workflow_details? +
The tool pulls detailed JSON logic nodes directly from your instance. This gives you full visibility into link mappings and trigger configurations, letting you understand the underlying data flow.
Can list_workflow_executions filter results to only show failed runs? +
Yes. You can use this tool to scope down your investigation by filtering executions based on status or time range. This helps narrow down thousands of logs to the specific failures you need.
Does this work with self-hosted n8n instances? +
Yes. You just need to provide your full n8n Base URL (e.g., https://n8n.your-company.com). Your agent will connect securely to your private instance using your n8n API Key.
Can I see exactly why an n8n execution failed through my agent? +
Yes. Use the get_execution tool with a specific Execution ID. Your agent will retrieve the node-level trace logs, allowing you to see which specific node encountered an error and the resulting output payload for that step.
Can my agent list the automation credentials saved in my n8n account? +
Absolutely. Use the list_credentials tool to identify all stored auth hooks. Your agent will report the credential names and system types (e.g., Slack, GitHub), helping you audit your integrations without exposing literal secure tokens.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Gitpod
Automate cloud development environments — create, start, and manage Gitpod workspaces and organizations directly from any AI agent.
Mailgun (Transactional Email & Domains)
Manage email infrastructure via Mailgun — send transactional emails, monitor domain health, and audit delivery logs.
Portainer
Manage Docker containers and environments via Portainer — list, create, and start containers directly from your AI agent.
You might also like
Pinterest Ads
Equip your AI agent with direct access to Pinterest Ads — manage campaigns, track pin performance, and optimize shopping ad spend without opening Pinterest Ads Manager.
Duffel
Search and book flights and stays directly through AI. Access real-time offers, manage orders, and explore travel metadata.
CoderPad
Manage technical interviews and assessments via CoderPad — create pads, track interview events, and audit the question bank directly from any AI agent.