mcp: Agent for Claude Code

.claude/agents/n8n-mcp-tester.md

n8n-mcp-tester is an agent for Claude Code from fatemehmollaeimdepended-cloud/mcp. It costs 375 tokens per session (1,941 once invoked), scanned A, a copy of n8n-mcp-tester, MIT.

An agent for testing an n8n Model Context Protocol (MCP) server with real n8n workflows. MCP lets an AI system use tools exposed by a server.

In plain words
What is it for?
Use it after fixes or new features to test n8n tools, positive and negative cases, edge conditions, and workflow operations.
Why use it?
It checks whether new or changed MCP functionality works in realistic workflows, beyond ordinary unit tests.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is fatemehmollaeimdepended-cloud/mcp's own configuration. It tells Claude Code how to work on mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to fatemehmollaeimdepended-cloud/mcp. 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/fatemehmollaeimdepended-cloud/mcp/main/.claude/agents/n8n-mcp-tester.md
Clone the repo
git clone --depth 1 https://github.com/fatemehmollaeimdepended-cloud/mcp

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.

agentmods badge for n8n-mcp-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/fatemehmollaeimdepended-cloud/mcp/n8n-mcp-tester/github.svg)](https://agentmods.dev/agents/fatemehmollaeimdepended-cloud/mcp/n8n-mcp-tester)
Your own site
<a href="https://agentmods.dev/agents/fatemehmollaeimdepended-cloud/mcp/n8n-mcp-tester"><img src="https://agentmods.dev/badge/agents/fatemehmollaeimdepended-cloud/mcp/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.

agentmods 80×15 button for n8n-mcp-tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/fatemehmollaeimdepended-cloud/mcp/n8n-mcp-tester"><img src="https://agentmods.dev/badge/agents/fatemehmollaeimdepended-cloud/mcp/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.

ModelPer sessionOnce 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 10d ago against content hash e6838c4341d4, 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 10d 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:

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

Testing Methodology

When invoked with a test request, you will:

  1. Understand the Context: Identify what was fixed or added based on the instructions from the invoking agent

  2. 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
  3. 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
  4. 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
  5. 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.

  1. 10d ago First seen · 102 lines · 375 tokens per session scan A e6838c4341d4

Subscribe to this mod's changes

n8n-mcp-tester is an agent published in the GitHub repository fatemehmollaeimdepended-cloud/mcp (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.

Related

Other agents, from other repositories

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

sdd-init

Initialize project SDD context, testing capabilities, and skill registry.

Gentleman-Programming/gentle-pi · 17 tokens

python-pro

Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.

echoVic/blade-code · 51 tokens

test-engineer

QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.

felvieira/claude-skills-fv · 66 tokens

test-writer

Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…

HirogaKatageri/hirokata · 77 tokens

implement-test-diversifier

Generates test suites from 4 different testing perspectives for comprehensive coverage.

eai-support/eai-gofer · 19 tokens