A
licenseC
qualityD
maintenanceEnables connecting MCP hosts like Claude to various productivity tools (Notion, Monday, Jira, etc.) through a secure no-code integration hub.
71
28 npm
MIT
WayStation MCP Server
Related Servers
Alternatives to WayStation MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceIntegrates Asana, GitHub, and Slack into MCP-compatible clients like Claude and Cursor, enabling task management, messaging, and project management through natural language.4 npmMIT
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP gateway that connects productivity tools like Jira, Confluence, and Obsidian to AI assistants via a single endpoint.2MIT
- AlicenseNot gradedqualityCmaintenanceConnects Claude Desktop to self-hosted enterprise tools such as Confluence, Jira, Bitbucket, Airtable, and databases (MySQL, MariaDB, ClickHouse, Oracle) via MCP.MIT
- 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
- 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.-
TDQS
B3.3/5.0
Scored across 71 tools
Disambiguation4/5
Tools are largely distinguishable due to the service prefix in each name (e.g., listNotionPages vs. listMondayBoards). Some subtle overlap exists within a service, such as readAsanaProject returning tasks and listAsanaTasks also returning tasks, but descriptions clarify the differences. Overall, the platform-prefixed naming prevents major confusion.
Naming Consistency4/5
The vast majority of tools follow a consistent verb + Service + Noun pattern (e.g., listNotionPages, createMondayItem, updateAsanaTask). Minor exceptions like recentOfficeDocs (no verb) and helloWayStation/openWayStation (descriptive non-standard) are present but do not significantly disrupt the overall pattern.
Tool Count1/5
With 71 tools, the server has an extreme number of operations, well beyond the recommended upper bound of 25. While the breadth reflects the many integrated services, the sheer count makes tool selection overwhelming for an agent and suggests potential redundancy across similar operations for different platforms.
Completeness3/5
The tool surface provides solid coverage for core workflows across many services: listing, reading, creating, and updating for most integrations. However, notable gaps exist, such as missing delete operations (e.g., no Notion page delete, no Monday item delete, no Asana task delete) and limited actions for some services (e.g., no Slack channel creation, no Gmail search). This makes the surface functional but not fully complete.
Maintenance
ActivityInactive
ResponsivenessSyncing