{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_86755crj-n9n","slug":"86755crj-n9n","name":"n9n","type":"mcp","url":"https://smithery.ai/servers/86755crj/n9n","page_url":"https://unfragile.ai/86755crj-n9n","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:86755crj/n9n"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_86755crj-n9n__cap_0","uri":"capability://tool.use.integration.mcp.protocol.server.instantiation.and.lifecycle.management","name":"mcp protocol server instantiation and lifecycle management","description":"Implements a Model Context Protocol server that exposes n9n workflow automation capabilities through the MCP standard interface. The server handles protocol negotiation, message routing, and resource lifecycle according to MCP specification, enabling Claude and other MCP-compatible clients to discover and invoke n9n operations as tools without direct API integration.","intents":["I want Claude to directly trigger n9n workflows without building custom integrations","I need to expose n9n automation capabilities to MCP-compatible AI clients","I want to standardize how AI agents interact with my n9n instance via a protocol layer"],"best_for":["Teams using Claude with n9n automation who want native MCP integration","Developers building multi-tool AI agents that need standardized protocol support","Organizations standardizing on MCP for AI-to-automation-platform communication"],"limitations":["MCP protocol overhead adds latency compared to direct REST API calls","Requires MCP-compatible client (Claude, or custom MCP client implementation)","No built-in session persistence — state management depends on client implementation","Protocol version compatibility must be maintained between server and client"],"requires":["n9n instance (version unknown from artifact metadata)","MCP-compatible client (Claude, Anthropic SDK, or custom MCP client)","Network connectivity between MCP server and n9n instance","Proper MCP server configuration and initialization"],"input_types":["MCP protocol messages (JSON-RPC 2.0 format)","Tool invocation requests with parameters","Resource discovery queries"],"output_types":["MCP protocol responses","Tool execution results","Resource metadata and schemas"],"categories":["tool-use-integration","mcp-server"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_86755crj-n9n__cap_1","uri":"capability://tool.use.integration.n9n.workflow.discovery.and.schema.exposure.via.mcp.resources","name":"n9n workflow discovery and schema exposure via mcp resources","description":"Exposes n9n workflows, credentials, and execution templates as discoverable MCP resources with JSON schemas. The server introspects the n9n instance to catalog available workflows and their input/output contracts, allowing MCP clients to dynamically discover what automation operations are available and their parameter requirements without hardcoding tool definitions.","intents":["I want Claude to see all available n9n workflows and their parameters automatically","I need dynamic workflow discovery so new n9n workflows are immediately available to AI clients","I want to expose n9n automation capabilities with proper schema validation to AI agents"],"best_for":["Teams with frequently changing n9n workflows who want AI agents to auto-discover new capabilities","Organizations building dynamic AI-to-automation bridges without manual tool registration","Developers integrating n9n with Claude who want schema-driven tool invocation"],"limitations":["Schema discovery latency depends on n9n instance size and network conditions","Complex nested workflow parameters may not translate cleanly to MCP schema format","Requires n9n API access with appropriate permissions to introspect workflows","Schema caching strategy not specified — may cause stale workflow definitions if n9n is updated"],"requires":["n9n instance with API access enabled","n9n API credentials with workflow read permissions","MCP client capable of parsing and using resource schemas","Network connectivity to n9n instance"],"input_types":["n9n workflow metadata","Workflow parameter definitions","Credential type schemas"],"output_types":["MCP resource definitions with JSON schemas","Workflow parameter contracts","Tool invocation schemas"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_86755crj-n9n__cap_2","uri":"capability://tool.use.integration.workflow.execution.triggering.with.parameter.mapping.and.result.streaming","name":"workflow execution triggering with parameter mapping and result streaming","description":"Implements MCP tool calling that maps Claude's tool invocation requests to n9n workflow executions, handling parameter transformation, execution queuing, and result streaming back through the MCP protocol. The server translates MCP tool call parameters into n9n workflow input format, monitors execution status, and streams results back to the client with proper error handling and timeout management.","intents":["I want Claude to trigger n9n workflows with specific parameters and get results back","I need to pass Claude's tool invocation parameters directly into n9n workflow inputs","I want to see n9n workflow execution results streamed back to Claude in real-time"],"best_for":["Teams using Claude to orchestrate n9n automation with dynamic parameters","Developers building AI agents that need to execute n9n workflows as part of reasoning chains","Organizations automating complex multi-step processes via Claude + n9n integration"],"limitations":["Execution latency depends on n9n workflow complexity and external API calls within workflows","Long-running workflows may exceed MCP client timeout windows — requires async polling strategy","Parameter type coercion between MCP schema types and n9n input types may lose precision","No built-in retry logic for failed workflow executions — depends on n9n's native retry configuration"],"requires":["n9n instance with workflow execution API enabled","n9n API credentials with workflow execution permissions","MCP client with tool calling support (Claude, Anthropic SDK)","Proper timeout and polling configuration for long-running workflows"],"input_types":["MCP tool invocation requests with parameters","Workflow input schemas","Execution context and metadata"],"output_types":["Workflow execution results","Execution status and logs","Error messages and stack traces"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_86755crj-n9n__cap_3","uri":"capability://tool.use.integration.credential.and.authentication.context.propagation","name":"credential and authentication context propagation","description":"Manages n9n credential context and authentication state within MCP tool invocations, allowing workflows to access stored credentials without exposing secrets to the MCP client. The server handles credential resolution, scope validation, and secure credential injection into workflow execution contexts, ensuring that Claude and other MCP clients can trigger authenticated workflows without direct credential access.","intents":["I want n9n workflows to use stored credentials without exposing them to Claude","I need to ensure Claude can trigger workflows that require authentication without handling secrets","I want to validate that Claude has permission to execute workflows with specific credentials"],"best_for":["Teams running n9n workflows that require external API authentication (Slack, GitHub, etc.)","Organizations with security policies requiring credential isolation from AI clients","Developers building AI agents that need to trigger authenticated workflows securely"],"limitations":["Credential scope validation depends on n9n's credential permission model — may not support fine-grained access control","No built-in audit logging for credential usage through MCP — requires external monitoring","Credential refresh tokens must be managed by n9n — MCP server cannot directly refresh credentials","Scope validation happens at execution time — no pre-flight permission checking for Claude"],"requires":["n9n instance with credential management enabled","Credentials stored in n9n for workflows being executed","n9n API access to credential metadata and scope information","Proper RBAC configuration in n9n for credential access control"],"input_types":["Workflow execution requests with credential references","Credential scope and permission metadata","MCP client identity and authorization context"],"output_types":["Credential validation results","Execution authorization decisions","Error messages for credential access violations"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_86755crj-n9n__cap_4","uri":"capability://tool.use.integration.workflow.execution.history.and.status.polling.via.mcp.resources","name":"workflow execution history and status polling via mcp resources","description":"Exposes n9n workflow execution history and real-time status as MCP resources that MCP clients can query and poll. The server maintains a queryable interface to execution logs, status updates, and result artifacts, allowing Claude and other clients to check workflow progress, retrieve historical executions, and access execution metadata without direct n9n API access.","intents":["I want Claude to check the status of a running n9n workflow","I need to retrieve execution history and logs for debugging workflow failures","I want Claude to query past workflow executions to inform decision-making"],"best_for":["Teams building AI agents that need to monitor long-running n9n workflows","Developers debugging workflow failures through Claude conversations","Organizations auditing workflow execution history through AI-driven queries"],"limitations":["Polling-based status updates introduce latency — no native webhook support for real-time updates","History query performance depends on n9n database size and indexing","Execution logs may be truncated or filtered by n9n retention policies","No built-in filtering or search optimization — queries may be slow on large execution histories"],"requires":["n9n instance with execution history API enabled","n9n API credentials with execution history read permissions","MCP client capable of polling resources","Adequate n9n database storage for execution history retention"],"input_types":["Workflow execution IDs","Date range filters","Status filter criteria","Pagination parameters"],"output_types":["Execution status and metadata","Execution logs and output data","Historical execution summaries","Error details and stack traces"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_86755crj-n9n__cap_5","uri":"capability://tool.use.integration.error.handling.and.execution.failure.recovery.with.retry.guidance","name":"error handling and execution failure recovery with retry guidance","description":"Implements structured error handling for workflow execution failures, capturing error context, failure reasons, and recovery suggestions. The server translates n9n execution errors into MCP error responses with actionable guidance, enabling Claude to understand why workflows failed and suggest remediation steps (parameter adjustment, credential refresh, etc.) without requiring manual n9n console inspection.","intents":["I want Claude to understand why an n9n workflow failed and suggest fixes","I need detailed error context from failed workflows to inform retry strategies","I want Claude to guide users through workflow failure recovery"],"best_for":["Teams using Claude to troubleshoot n9n workflow failures in conversation","Developers building AI agents that need to handle and recover from workflow errors","Organizations automating error recovery and remediation through Claude"],"limitations":["Error context richness depends on n9n's error reporting — some failures may lack detailed context","Retry guidance is heuristic-based — may not cover all failure scenarios","No automatic retry execution — Claude must explicitly request retry through tool calling","Transient vs permanent failures may not be clearly distinguished in error responses"],"requires":["n9n instance with detailed error logging enabled","n9n API access to execution error details","MCP client capable of interpreting structured error responses","Error classification logic in MCP server implementation"],"input_types":["n9n execution error objects","Workflow context and parameters","Execution attempt history"],"output_types":["Structured error responses with error codes","Error descriptions and root cause analysis","Recovery suggestions and remediation steps","Retry guidance and parameter adjustment recommendations"],"categories":["tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":24,"verified":false,"data_access_risk":"high","permissions":["n9n instance (version unknown from artifact metadata)","MCP-compatible client (Claude, Anthropic SDK, or custom MCP client)","Network connectivity between MCP server and n9n instance","Proper MCP server configuration and initialization","n9n instance with API access enabled","n9n API credentials with workflow read permissions","MCP client capable of parsing and using resource schemas","Network connectivity to n9n instance","n9n instance with workflow execution API enabled","n9n API credentials with workflow execution permissions"],"failure_modes":["MCP protocol overhead adds latency compared to direct REST API calls","Requires MCP-compatible client (Claude, or custom MCP client implementation)","No built-in session persistence — state management depends on client implementation","Protocol version compatibility must be maintained between server and client","Schema discovery latency depends on n9n instance size and network conditions","Complex nested workflow parameters may not translate cleanly to MCP schema format","Requires n9n API access with appropriate permissions to introspect workflows","Schema caching strategy not specified — may cause stale workflow definitions if n9n is updated","Execution latency depends on n9n workflow complexity and external API calls within workflows","Long-running workflows may exceed MCP client timeout windows — requires async polling strategy","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.38999999999999996,"match_graph":0.25,"freshness":0.5,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:25.061Z","last_scraped_at":"2026-05-03T15:19:42.883Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=86755crj-n9n","compare_url":"https://unfragile.ai/compare?artifact=86755crj-n9n"}},"signature":"VeeRaRhLipYoGIF039XMJhksxTFmrT2jdSo/P9TdrT76dtF0bD4Pku+QxrtNOtNMrYy3nYpX94HXyWzY6b2bDw==","signedAt":"2026-06-23T06:45:23.710Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/86755crj-n9n","artifact":"https://unfragile.ai/86755crj-n9n","verify":"https://unfragile.ai/api/v1/verify?slug=86755crj-n9n","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}