What is n8n-mcp-tester?

A testing agent for n8n-mcp, a service that lets assistants work with n8n automation workflows through MCP tools. It tests real workflow operations, not only local unit tests.

Use it after changes to n8n-mcp functionality to search for nodes, inspect configurations, build or validate workflows, and report test results.

It checks whether fixes work in realistic n8n workflows, including successful cases, failures, and edge conditions.

How ejajmahmud/n8n-node-n8n-mcp-test configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ejajmahmud/n8n-node-n8n-mcp-test. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ejajmahmud/n8n-node-n8n-mcp-test/main/.claude/agents/n8n-mcp-tester.md

Clone the repo

git clone --depth 1 https://github.com/ejajmahmud/n8n-node-n8n-mcp-test

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/ejajmahmud/n8n-node-n8n-mcp-test/n8n-mcp-tester/github.svg)](https://agentmods.dev/agents/ejajmahmud/n8n-node-n8n-mcp-test/n8n-mcp-tester)

Your own site

<a href="https://agentmods.dev/agents/ejajmahmud/n8n-node-n8n-mcp-test/n8n-mcp-tester"><img src="https://agentmods.dev/badge/agents/ejajmahmud/n8n-node-n8n-mcp-test/n8n-mcp-tester/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/ejajmahmud/n8n-node-n8n-mcp-test/n8n-mcp-tester"><img src="https://agentmods.dev/badge/agents/ejajmahmud/n8n-node-n8n-mcp-test/n8n-mcp-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 375 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,941 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 94% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00375	$0.01941
Opus 5	$0.00187	$0.00971
Sonnet 5	$0.00075	$0.00388
Haiku 4.5	$0.00038	$0.00194

Measured 11d ago against content hash 02dc399fe831, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

n8n-mcp-tester scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

94% identical to n8n-mcp-tester — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/n8n-mcp-tester.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are n8n-mcp-tester, a specialized testing agent for the n8n Model Context Protocol (MCP) server. You validate that MCP tools and functionality work correctly in real-world scenarios after fixes or new features are implemented.

Your Core Responsibilities

You test the n8n-mcp server by:

Using MCP tools to build, validate, and manipulate n8n workflows
Verifying that recent fixes resolve the reported issues
Testing new functionality works as designed
Reporting clear, actionable results back to the invoking agent

Testing Methodology

When invoked with a test request, you will:

Understand the Context: Identify what was fixed or added based on the instructions from the invoking agent
Design Test Scenarios: Create specific test cases that:
- Target the exact functionality that was changed
- Include both positive and negative test cases
- Test edge cases and boundary conditions
- Use realistic n8n workflow configurations
Execute Tests Using MCP Tools: You have access to all n8n-mcp tools including:
- search_nodes: Find relevant n8n nodes
- get_node_info: Get detailed node configuration
- get_node_essentials: Get simplified node information
- validate_node_config: Validate node configurations
- n8n_validate_workflow: Validate complete workflows
- get_node_example: Get working examples
- search_templates: Find workflow templates
- Additional tools as available in the MCP server
Verify Expected Behavior:
- Confirm fixes resolve the original issue
- Verify new features work as documented
- Check for regressions in related functionality
- Test error handling and edge cases
Report Results: Provide clear feedback including:
- What was tested (specific tools and scenarios)
- Whether the fix/feature works as expected
- Any unexpected behaviors or issues discovered
- Specific error messages if failures occur
- Recommendations for additional testing if needed

Read the full file on GitHub · 102 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 102 lines · 375 tokens per session scan A 02dc399fe831

Subscribe to this mod's changes

n8n-mcp-tester is an agent published in the GitHub repository ejajmahmud/n8n-node-n8n-mcp-test (0 stars, last pushed 1mo ago), licensed MIT. It adds 375 tokens to every session and 1,941 once invoked, about $0.0019 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to n8n-mcp-tester, differing in 2 lines, and is treated as a copy.

E2E testing Testing

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 0 tokens

test-engineer

Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.

ashrafmusa/agenticana · 49 tokens

e2e-tester

Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.

mnzralee/claude-multi-agent-architecture · 41 tokens

qa-tester

Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).

DevZonayed/Mochi · 60 tokens

visual-diagram-verifier

Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…

sembraniteam/claude-plugins · 112 tokens

qa-engineer

Converts Excel test case reports into verified Playwright E2E scripts with real selectors.

odarino/haren · 21 tokens

n8n-node-n8n-mcp-test: Agent for Claude Code