Pulse Workflow MCP Server
OfficialRelated Servers
Alternatives to Pulse Workflow MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceWraps Claude Code as tools for MCP clients, enabling autonomous coding tasks via a 4-tool lifecycle with session management, async polling, and permission controls.434 npm20MIT
- FlicenseNot gradedqualityCmaintenanceExposes Claude Code's file editing, command execution, and test running capabilities as composable MCP tools for any MCP-compatible host, enabling code operations via a stateless bridge.-
- AlicenseBqualityCmaintenanceExposes your LLMGraph workflow deployments as MCP tools, allowing AI assistants to invoke them via natural language.127 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to programmatically create, manage, and orchestrate n8n workflows through a standardized MCP interface.MIT

IBM Business Automationofficial
AlicenseNot gradedqualityCmaintenanceEnables 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.10Apache 2.0- FlicenseNot gradedqualityCmaintenanceExposes declarative Prompt flow workflows as individual MCP tools, allowing generalist agents to invoke deterministic, isolated, and permission-bound operations without custom code.-
TDQS
Scored across 36 tools
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.
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.
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.
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.