Skip to main content
Glama
enesjakozh
onurpolat05

n8n-asistans

by onurpolat05
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

n8n 助手

铁匠徽章

该项目包含一个多渠道平台 (MCP) 服务器，用于创建与 n8n 集成的助手。该助手可用于搜索 n8n 文档、示例工作流程和社区论坛。

特征

  • 网络搜索：根据特定查询搜索 n8n 文档、工作流程和社区论坛。

  • HTML 内容获取：使用 BeautifulSoup 从搜索结果中提取主要内容。

  • 异步处理：异步执行 HTTP 请求，提供更快的响应时间。

Related MCP server: n8n MCP Server

要求

  • Python 3.7 或更高版本

  • httpx库

  • beautifulsoup4库

  • python-dotenv库

安装

通过 Smithery 安装

要通过Smithery自动为 Claude Desktop 安装 n8n-assistant：

npx -y @smithery/cli install @onurpolat05/n8n-assistant --client claude

手动安装

  1. 克隆此存储库：

    git clone <repository-url>
cd <repository-directory>

  2. 安装所需的依赖项：

    pip install -r requirements.txt

  3. 创建一个.env文件并添加必要的 API 密钥：

    SERPER_API_KEY=your_api_key_here

用法

要启动助手，请运行以下命令：

uvicorn main:app --reload

然后，您可以向助手查询与 n8n 相关的信息，如下所示：

await get_n8n_info("HTTP Request node", "docs")

MCP 服务器

该项目使用n8n-asistans MCP 服务器。该服务器使用以下命令启动：

{
    "mcpServers": {
        "n8n-asistans": {
            "command": "uv",
            "args": [
                "--directory",
                "/n8n-assistant",
                "run",
                "main.py"
            ],
            "env":{
                "SERPER_API_KEY": "*********"
            }
        }
    }
}

贡献

如果您想做出贡献，请创建拉取请求或报告问题。

执照

该项目已获得 MIT 许可。

Available Tools

1 tool
get_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

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes
resource_typeYes

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'latest n8n resources' but lacks details on permissions, rate limits, error handling, or response format beyond 'Text from the n8n resources,' leaving significant gaps for a search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a purpose statement, args section, and returns section, making it easy to parse. It could be slightly more concise by integrating the parameter details more fluidly, but overall it's efficient with minimal waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low complexity, the description covers the basic purpose and parameters adequately. However, it lacks details on behavioral aspects like search limitations or result formatting, making it minimally viable but incomplete for optimal agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 0%, the description fully compensates by clearly explaining both parameters: 'query' as the search term with an example and 'resource_type' with detailed options (docs, workflows, community) and their meanings. This adds substantial value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as 'Search the latest n8n resources for a given query,' which specifies the verb (search) and resource (n8n resources). However, with no sibling tools provided, it cannot demonstrate differentiation from alternatives, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It only lists parameters and returns, offering no context for decision-making in usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedget_n8n_info
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • axiom8-mcp

    alexandre-axioma
    F
    license
    Not graded
    quality
    D
    maintenance
    AI-powered n8n documentation server that enables intelligent semantic search and retrieval of node configurations, workflows, and templates for AI assistants.
    -

  • n8n MCP Server

    Nielsen642
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to access comprehensive n8n node documentation, properties, and operations for building workflow automations.
    93,909 npm
    MIT

  • n8n-MCP

    clanker25
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables 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.
    93,909 npm
    MIT

Appeared in Searches