Skip to main content
Glama
workflow86oss

Workflow86 MCP Server

Official
by workflow86oss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Workflow86 MCP Server

No user-submitted related servers found.

    Related Servers

    • n8n-free-mcp

      jserna0001
      A
      license
      A
      quality
      C
      maintenance
      Free and open-source MCP server for managing n8n workflows, executions, and tags via n8n's API. Enables workflow creation, activation, debugging, and deletion from any MCP client.
      12
      2
      MIT

    • mcp-n8n

      lyzetam
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for n8n workflow automation, enabling management of workflows, executions, credentials, tags, users, and webhooks via an MCP-compatible client.
      MIT

    • n8n MCP Server

      allanbchancery
      A
      license
      B
      quality
      D
      maintenance
      MCP server for managing n8n workflows and executions. Enables listing, activating, deactivating, and executing workflows, as well as monitoring executions and instance health.
      9
      MIT

    • mcp-n8n-builder

      spences10
      A
      license
      A
      quality
      D
      maintenance
      🪄 MCP server for programmatic creation and management of n8n workflows. Enables AI assistants to build, modify, and manage workflows without direct user intervention through a comprehensive set of tools and resources for interacting with n8n's REST API.
      10
      28 npm
      86
      MIT
    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

    A3.5/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct operation—workflows, sessions, tasks, forms, tables, and component manipulation—with clear boundaries. Even similar actions like 'terminate-entire-session' and 'terminate-component' are differentiated by scope.

    Naming Consistency5/5

    All tool names follow a consistent 'verb_noun' pattern (e.g., list-workflows, create-table, delete-component). No mixing of conventions or ambiguous verbs.

    Tool Count4/5

    22 tools is slightly above the typical 3-15 range, but the broad domain (workflows, sessions, tables, forms) justifies the number. It is not excessive and each tool serves a clear purpose.

    Completeness2/5

    The tool surface has significant gaps: no create/delete workflow, no table delete/update, only list operations for forms and tasks. Essential CRUD operations are missing, limiting agent capabilities.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources