WXO Builder MCP Server
Related Servers
Alternatives to WXO Builder MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI clients such as Claude, Cursor, VS Code, and Windsurf to list and manage workspaces, projects, tasks, AI agents, and automations through a hosted OAuth-secured endpoint or a local stdio package. Also generates MCP tools from any OpenAPI spec.3,240 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude, Cursor, VS Code, Windsurf, and other MCP clients to manage workspaces, projects, tasks, and AI agents through natural language, using a hosted OAuth server or local stdio package.3,240 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants like Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through natural language, with a hosted OAuth server or a local stdio package. Also supports generating MCP tools from any OpenAPI spec.3,240 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients such as Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through natural language, using a hosted OAuth-authenticated endpoint or a local stdio package. It also ships an OpenAPI codegen tool for generating MCP tools from any OpenAPI spec.3,240 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, AI agents, and app files through hosted OAuth or local stdio tools. It also includes OpenAPI codegen for generating MCP tools from any OpenAPI specification.3,240 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP 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.81 npmApache 2.0
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.