WXO Builder MCP Server
Related Servers
Alternatives to WXO Builder MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP gateway that lifts watsonx Orchestrate Slack limitations — every-message wake-up, multi-channel→multi-agent routing, clean in-thread replies, and a streamable-http toolkit for WxO + Cursor / VS Code / Bob / Antigravity — without replacing your agents.48 npmApache 2.0
- AlicenseCqualityBmaintenanceMCP server for IBM Concert Operate that exposes the full v2 REST API as callable tools, enabling AI assistants to manage alerts, incidents, policies, runbooks, and more.975 npm1MIT
- FlicenseNot gradedqualityCmaintenanceExposes n8n's REST API and local Ollama as MCP tools, allowing natural language instructions to create, execute, and monitor workflows from MCP clients like VS Code Copilot Chat.-
- AlicenseCqualityBmaintenanceMCP server to connect Claude Code, Codex, or Cursor to the Lightbulb Partners Agents platform, enabling domain agents, code workspaces, connectors, and more.500416 PyPIApache 2.0
- AlicenseAqualityDmaintenance🪄 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.1023 npm86MIT
- AlicenseAqualityAmaintenanceMCP server for Cognigy.AI - 132 tools that let Claude, Cursor & other AI assistants build, configure, test & operate conversational AI agents via the Model Context Protocol.10033 npm2MIT
TDQS
Scored across 35 tools
There are overlapping list tools (list_skills, list_standard_tools, list_tools_with_connections) that could cause confusion, and execute_tool vs test_tool_local both invoke functionality but through different paths. However, the detailed descriptions with usage hints help an agent differentiate between them.
All tool names follow a consistent verb_noun snake_case pattern (e.g., list_agents, get_agent, create_connection, delete_flow). Even compound names like create_tool_and_assign_to_agent and update_agent_instructions_from_tools maintain the pattern, making the naming predictable and uniform.
With 35 tools, the server is on the heavy side, but the scope is broad, covering agents, skills/tools, connections, and flows. Some tools could be consolidated (e.g., list_standard_tools and list_tools_with_connections overlap with list_skills), but the count is justifiable for a comprehensive builder API.
The tool surface is exceptionally complete for the stated domain. It covers full CRUD lifecycle for agents (list, create, get, update, delete, invoke), skills/tools (list, get, deploy, update, delete, copy, execute, assign), connections (list, get, create, configure, delete), and flows (list, create, get, delete) plus API discovery via get_api_spec. No obvious gaps or dead ends are present.