Skip to main content
Glama
enesjakozh
onurpolat05

n8n-asistans

by onurpolat05
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

n8n 어시스턴트

대장간 배지

이 프로젝트에는 n8n과 통합된 어시스턴트를 만드는 데 사용되는 다중 채널 플랫폼(MCP) 서버가 포함되어 있습니다. 어시스턴트를 사용하여 n8n 문서, 예제 워크플로 및 커뮤니티 포럼을 검색할 수 있습니다.

특징

  • 웹 검색 : 특정 쿼리를 기반으로 n8n 문서, 워크플로, 커뮤니티 포럼을 검색합니다.

  • HTML 콘텐츠 가져오기 : BeautifulSoup를 사용하여 검색 결과에서 주요 콘텐츠를 추출합니다.

  • 비동기 처리 : HTTP 요청을 비동기적으로 수행하여 응답 시간을 더 빠르게 제공합니다.

Related MCP server: n8n MCP Server

요구 사항

  • Python 3.7 이상

  • httpx 라이브러리

  • beautifulsoup4 라이브러리

  • python-dotenv 라이브러리

설치

Smithery를 통해 설치

Smithery를 통해 Claude Desktop용 n8n-assistant를 자동으로 설치하려면:

지엑스피1

수동 설치

  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