WayStation MCP Server
Related Servers
Alternatives to WayStation MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceConnects AI assistants like Claude to productivity tools such as Notion, Monday, Jira, and Slack via a remote MCP integration hub.7128 npmMIT
- AlicenseBqualityDmaintenanceEnables seamless and secure connectivity between MCP hosts (like Claude Desktop, Cline, or Cursor) and productivity tools through WayStation's no-code integration hub.7128 npm62MIT

mcpgateofficial
FlicenseNot gradedqualityBmaintenanceSelf-hosted MCP gateway that connects Claude, ChatGPT, and other AI agents to 20+ enterprise tools (GitLab, Jira, Notion, Google Workspace, Slack, Grafana, …) with OAuth, audit logs, and zero data leaving your infrastructure-
AllMCPofficial
AlicenseNot gradedqualityBmaintenanceOpen-source MCP hub providing a single endpoint for AI agents to access dozens of business integrations (CRMs, spreadsheets, telephony, ads) with multi-tenancy, OAuth, and context-efficient tool discovery.Apache 2.0- FlicenseNot gradedqualityCmaintenanceProvides AI agents with 220+ tools for building websites, sending email, managing contacts, invoicing, databases, automation, and more through a single secure connection. Features hardware-bound authentication and works with Claude Desktop, Claude Code, Cursor, and other MCP-compatible clients.-
- AlicenseNot gradedqualityAmaintenanceMCP Hub is a self-hosted AI operations platform that provides a unified MCP gateway with semantic tool routing, persistent vector memory, automation, and multi-agent flows. It enables connecting any MCP client to 130+ tools across 12 integrations through just 3 hub endpoints.4MIT
TDQS
Scored across 71 tools
While most tools target a specific resource and action, there is notable overlap across similar tools (e.g., readLinearProject includes all issues while listLinearIssues also lists issues, and listAsanaProjects/readAsanaProject/listAsanaTasks/task searching have blurred boundaries). Tool names and descriptions help disambiguate, but the sheer number of parallel CRUD operations across many apps increases the chance of selecting the wrong one.
The naming generally follows a consistent pattern of verb + provider + resource (e.g., listJiraProjects, createLinearIssue), but the verbs are inconsistent: getMiroBoard vs readJiraProject vs fetchPostgreSQLSchema, and create vs add vs post for similar actions (createJiraComment, addJiraComment, postMiroNote). Also, helloWayStation and openWayStation deviate from the convention, making the set feel somewhat mixed.
With 71 tools, the server is far beyond the typical well-scoped range. Although it aggregates many integrations, the high count reflects a broad but shallow surface across 15+ services. This is an extreme number that will overwhelm agents and complicate tool selection.
The tool surface covers core workflows for a wide array of apps (Jira, Linear, Asana, Gmail, etc.) but has notable gaps: no delete operations in most apps, no update for Miro/Notion docs, and read-only database access. Some integrations lack essential actions (e.g., Teams cannot read channel history, Office docs cannot be created/edited). Overall, the set is broad but not deep, with agents likely hitting dead ends for modifications beyond basic creation and updates.