Skip to main content
Glama
Pulse-Intelligence

Pulse Workflow MCP Server

Official
by Pulse-Intelligence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Pulse Workflow MCP Server

No user-submitted related servers found.

    Related Servers

    • claude-code-mcp

      xihuai18
      A
      license
      A
      quality
      D
      maintenance
      Wraps Claude Code as tools for MCP clients, enabling autonomous coding tasks via a 4-tool lifecycle with session management, async polling, and permission controls.
      4
      64 npm
      20
      MIT

    • n8n MCP Server

      MrBozkay
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to programmatically create, manage, and orchestrate n8n workflows through a standardized MCP interface.
      MIT

    • Forja MCP Server

      gilsonfiho
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes specialized agents as MCP tools so users can manage and triage Jira tasks, analyze repositories for health and conventions, generate commit/PR/DevOps patterns, assemble reports, produce slides and infographics, and run semantic search over a knowledge base. Everything is invokable directly from inside a coding session in Claude Code, Cursor, or Claude Desktop.
      MIT
    • IBM Business Automation Workflow MCP Server by ibmbpm

      IBM Business Automationofficial

      ibmbpm
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to integrate with IBM Business Automation Workflow by exposing workflow REST services as MCP tools, allowing natural language interaction with business automation capabilities.
      11
      Apache 2.0
    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

    C2.7/5.0

    Scored across 36 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource (nodes, notes, apps, workflows, datasets, agent strategies, etc.). No overlaps or ambiguous boundaries; even batch_add_nodes is clearly a bulk variant of add_node.

    Naming Consistency5/5

    All tools use consistent verb_noun snake_case naming (e.g., add_node, list_nodes, get_node_schema, batch_add_nodes). No mixing of conventions like camelCase or different verb styles.

    Tool Count2/5

    With 36 tools, this far exceeds the typical well-scoped range of 3-15. While the server covers a broad domain, the number of tools feels heavy and could overwhelm agents.

    Completeness4/5

    The tool set covers CRUD for nodes and notes, plus workflow lifecycle (initialize, validate, publish), and supporting functions (schemas, testing, search). Minor gaps: missing delete for apps and workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources