Skip to main content
Glama
mcp-n8n-voice-orchestrator

mcp-n8n-voice-orchestrator

Related Servers

Alternatives to mcp-n8n-voice-orchestrator

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Wraps the n8n self-hosted REST API to let Claude and MCP-compatible LLMs manage workflows, executions, credentials, and more via natural language.
      39
      128 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables users to manage workflows, monitor executions, and perform administrative tasks in n8n through natural language conversations with Claude. It provides over 40 tools to control self-hosted or cloud n8n instances via the Model Context Protocol.
      42
      128 npm
      MIT
    • F
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to fully automate n8n instances via 34 MCP tools, covering workflow creation, execution debugging, credential management, environment variables, tags, and user administration through natural language.
      34
      1
      -
    • A
      license
      A
      quality
      C
      maintenance
      Full-instance management for self-hosted n8n — including queue mode — through the Model Context Protocol. 51 tools covering workflows, executions, tags, credentials, variables, projects, users, security audit, source control and health monitoring. n8n-pro-mcp connects Claude Code, Claude Desktop, Cursor or any MCP client to your n8n instance via the official n8n public API v1
      51
      38 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Production-ready MCP server that brings N8N workflow automation to both Claude.ai and ChatGPT. Supports multi-tenant OAuth/SSE integration with dynamic N8N instance configuration.
      128 npm
      MIT

    TDQS

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of confusing it with another; its purpose as a workflow dispatcher is unmistakable.

    Naming Consistency4/5

    The lone name follows a clear snake_case verb_noun pattern (dispatch_idempotent_n8n_workflow), though with one tool there is no pattern to actually be consistent across.

    Tool Count2/5

    A single tool is too thin for an orchestration server; dispatch is the only operation, leaving no room for status, verification, or management operations.

    Completeness2/5

    The surface offers fire-and-forget dispatch with no way to check workflow status, list available workflows, or handle failures, which are significant gaps for an orchestration role.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues