Agent Claude Code
name: code-reviewer description: Use this agent when you need to review recently written or modified code for quality, security, and maintainability. This agent should be invoked immediately after code changes are made to ensure high standards are maintained. Examples:\n\n \nContext: The user has created a code-review…
Agent Claude Code
Agent "context-manager" from lucas-denzer/n8n-mcp, covering primary functions, context capture, context distribution, memory management and workflow integration.
Agent Claude Code
name: debugger description: Use this agent when encountering errors, test failures, unexpected behavior, or any issues that require root cause analysis. The agent should be invoked proactively whenever debugging is needed. Examples:\n\n \nContext: The user encounters a test failure while running the test suite.\nuser…
Agent Claude Code
Agent "deployment-engineer" from lucas-denzer/n8n-mcp, covering core responsibilities, technical expertise, ci/cd pipelines, container engineering and kubernetes orchestration.
Agent Claude Code
name: mcp-backend-engineer description: Use this agent when you need to work with Model Context Protocol (MCP) implementation, especially when modifying the MCP layer of the application. This includes implementing new MCP tools, updating the MCP server, debugging MCP-related issues, ensuring compliance with MCP…
Agent Claude Code
Use this agent when you need to test n8n-mcp functionality after implementing fixes or new features. This agent should be invoked proactively after code changes to validate that the MCP tools work correctly with real n8n workflows. The agent tests the actual MCP server tools, not just unit tests. Examples:\n\n…
Agent Claude Code
Agent "technical-researcher" from lucas-denzer/n8n-mcp, covering core capabilities, research methodology, 1. query analysis phase, 2. information gathering phase and 3. validation phase.
Agent Claude Code
Agent "test-automator" from lucas-denzer/n8n-mcp, covering core responsibilities, testing philosophy, implementation guidelines, unit testing and integration testing.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: