n8n-asistans
This n8n Assistant server allows you to search and retrieve information from n8n resources:
Search Documentation: Find relevant n8n documentation for specific queries
Search Example Workflows: Find example workflows using
"n8n example {query}"Search Community Forums: Access discussions and solutions for n8n-related issues
Asynchronous Processing: Perform searches efficiently with asynchronous HTTP requests
Extract HTML Content: Use BeautifulSoup to clean web page results
Provides tools for searching n8n documentation, example workflows, and community forums, enabling users to find relevant information about n8n functionality and usage patterns.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@n8n-asistans show me example workflows for sending automated emails"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
n8n Assistant
This project contains a Multi-Channel Platform (MCP) server used to create an assistant integrated with n8n. The assistant can be used to search for n8n documentation, example workflows, and community forums.
Features
Web Search: Searches n8n documentation, workflows, and community forums based on a specific query.
HTML Content Fetching: Uses BeautifulSoup to extract the main content from search results.
Asynchronous Processing: Performs HTTP requests asynchronously, providing faster response times.
Related MCP server: n8n MCP Server
Requirements
Python 3.7 or higher
httpxlibrarybeautifulsoup4librarypython-dotenvlibrary
Installation
Installing via Smithery
To install n8n-assistant for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @onurpolat05/n8n-assistant --client claudeManual Installation
Clone this repository:
git clone <repository-url> cd <repository-directory>Install the required dependencies:
pip install -r requirements.txtCreate a
.envfile and add the necessary API keys:SERPER_API_KEY=your_api_key_here
Usage
To start the assistant, run the following command:
uvicorn main:app --reloadThen, you can query the assistant for information related to n8n like this:
await get_n8n_info("HTTP Request node", "docs")MCP Server
This project uses the n8n-asistans MCP server. The server is started with the following command:
{
"mcpServers": {
"n8n-asistans": {
"command": "uv",
"args": [
"--directory",
"/n8n-assistant",
"run",
"main.py"
],
"env":{
"SERPER_API_KEY": "*********"
}
}
}
}Contributing
If you would like to contribute, please create a pull request or report issues.
License
This project is licensed under the MIT License.
Available Tools
1 toolget_n8n_infoB
Search the latest n8n resources for a given query.
Args: query: The query to search for (e.g. "HTTP Request node") resource_type: The resource type to search in (docs, workflows, community) - docs: General n8n documentation - workflows: Example workflows (will search for "n8n example {query}") - community: Community forums for issues and questions
Returns: Text from the n8n resources
Inputs: query (required), resource_type (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, making disambiguation perfect. The tool's purpose is clearly defined as searching n8n resources, and no other tools exist to cause confusion.
Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name 'get_n8n_info' follows a clear verb_noun pattern, but consistency across multiple tools cannot be assessed.
A single tool for a server named 'n8n-asistans' feels too thin for the apparent scope, as it only offers search functionality without any CRUD operations or broader management capabilities for n8n resources. This is a borderline case leaning toward inadequacy for a typical assistant server.
The tool surface is severely incomplete for an assistant server, as it only provides search functionality without any ability to create, update, delete, or manage n8n workflows or resources. This will likely cause agent failures when trying to perform comprehensive tasks beyond simple queries.
Maintenance
Related MCP Connectors
Connect an AI assistant to a Capacities space (objects, daily notes, search).
Build, check and fix n8n workflows from Claude, Cursor or ChatGPT. Built on 1,100+ real n8n node definitions and curated templates, with a validator that repairs common mistakes (wrong node types, missing settings) and returns JSON ready to import into n8n. Sign in with a free gydmation.com account; nothing to install.
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analy…
Make how-to videos, social clips and help articles from Claude or ChatGPT, and run your help center.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAI-powered n8n documentation server that enables intelligent semantic search and retrieval of node configurations, workflows, and templates for AI assistants.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access comprehensive n8n node documentation, properties, and operations for building workflow automations.52,905 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search, validate, and manage n8n workflows, providing structured access to over 1,800 node documentations and templates.2652,905 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to access comprehensive n8n node documentation, properties, operations, workflow templates, and community nodes, allowing them to design, build, and validate n8n workflows through natural language.52,905 npmMIT