WayStation MCP Server
Allows AI agents to interact with Airtable bases, tables, and records for data retrieval, creation, and updates, enabling database management and workflow automation.
Provides tools for managing Asana projects, tasks, and activities, enabling task assignment, progress tracking, and project coordination.
Enables integration with Atlassian products such as Jira and Confluence, allowing project management, issue tracking, and documentation collaboration.
Allows AI agents to create, read, and update Confluence pages and spaces, facilitating knowledge management and documentation.
Provides access to Google Drive files and folders, including Google Docs and Sheets, enabling file management, content creation, and data retrieval.
Allows AI agents to interact with Intercom conversations, contacts, and messages, enabling customer support automation and communication.
Provides tools for managing Jira projects, issues, and workflows, enabling issue tracking, sprint management, and reporting.
Allows AI agents to manage Linear issues, projects, and teams, enabling task tracking, project planning, and workflow automation.
Enables interaction with Miro boards, frames, and widgets, facilitating brainstorming, diagramming, and collaboration on visual content.
Allows AI agents to access and manage Notion pages, databases, and workspaces, enabling note-taking, project management, and knowledge sharing.
Provides tools for handling PayPal payments, transactions, and invoices, enabling payment processing and financial management.
Allows AI agents to send messages, create channels, and manage Slack conversations, enabling team communication and collaboration.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@WayStation MCP Server create a Jira ticket for the bug report from Slack"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
What is WayStation
WayStation connects Claude Desktop, ChatGPT and any MCP host with the productivity tools you use daily such as Notion, Monday, Airtable, Jira etc. through a no-code, secure integration hub.
The original local WayStation MCP server has been deprecated in favor of the new remote MCP server hosted at https://waystation.ai/mcp. Please refer to the new WayStation MCP server documentation here
Overview
WayStation MCP server is a universal remote MCP server that seamlessly connects Claude (and other clients) to a broad range of productivity tools, including Notion, Monday, AirTable, etc.
WayStation MCP supports both Streamable HTTPS and SSE transports
The default endpoint is https://waystation.ai/mcp. It does transport negotiation and authorization if necessary
WayStation also provides preauthenticated individual endpoints like https://waystation.ai/mcp/Iddq66dIdkfARDNb3K. Any registered user can get one in their dashboard at https://waystation.ai/dashboard
Related MCP server: Corben MCP Server
Supported providers
WayStation supports the following productivity apps: Notion, Monday, Asana, Linear, Atlassian JIRA/Confluence, Slack, Teams, Google Drive (including Docs and Sheets), Office 365, Airtable, Miro, Intercom, PayPal.
Users can browse available integrations/providers in the Integrations Marketplace
New integrations are added regularly based on customer requests or community contributions. If you have an integration request, please contact us at support@waystation.ai.
Users can connect their apps in the dashboard. The connection process may vary by app but generally involves OAuth2 authentication flow with some additional steps for certain apps.
Supported AI apps
WayStation remote MCP was tested with Claude, Cursor, Cline, WindSurf, and MCP-remote STDIO proxy provider
For Claude, user should go into their Settings, then Integrations and click "Add Integration". Then enter "WayStation" as the Server Name and unique MCP URL from user's dashboard
For Cline, user should simply go into the MCP Server screen, switch to the Remote Servers tab, enter "WayStation" as the Server Name and unique MCP URL from user's dashboard
For Cursor, user should go to the Cursor Settings, MCP tab and click "Add new global MCP server". In mcp.json file user should add the entry for WayStation as following:
"WayStation": {
"url": "https://waystation.ai/mcp/<user_unique_id>"
}Use Cases
WayStation supports a variety of productivity and automation use cases listed below:
Available Tools
71 toolsaddJiraCommentB
Adds a new comment to an existing Jira issue.
Inputs: comment (required), issueKey (required).
applyGmailMessageLabelsA
Adds or removes labels from a Gmail message. This can be used to label drafts, sent emails, or any existing message in the user's Gmail account.
Inputs: messageId (required), addLabelIds, removeLabelIds.
createAirtableRecordB
Creates a new record with the specified fields in the given table
Inputs: baseId (required), fields (required), tableId (required).
createAsanaCommentA
Creates a new comment (story) on the specified Asana task.
Inputs: text (required), taskId (required).
createAsanaTaskB
Creates a new task in the specified Asana project with optional details like description, due date, assignee, and custom fields.
Inputs: name (required), projectId (required), custom_fields (required), notes, +2 more.
createJiraIssueB
Creates a new issue in a specified Jira project with the provided details.
Inputs: summary (required), projectKey (required), description (required), issueTypeId (required), +2 more.
createLinearCommentA
Creates a new comment on an existing issue in Linear.
Inputs: body (required), issueId (required).
createLinearIssueC
Creates a new issue in Linear with the specified details.
Inputs: title (required), teamId (required), stateId, priority, +3 more.
createMondayItemA
Creates a new item in the specified Monday board and group with optional column values. The column_values parameter should follow the format { "column_id": "value" } for each column to be set.
Inputs: board_id (required), group_id (required), item_name (required), column_values.
createMondayUpdateA
Creates a new update (comment) on the specified Monday.com item with optional parent_id for threaded replies.
Inputs: body (required), item_id (required), parent_id.
createNotionCommentA
Adds a plain text comment to a Notion page.
Inputs: text (required), pageId (required).
createNotionPageB
Creates a new page in Notion with specified content.
Inputs: title (required), parentId (required), parentType (required), content.
executeNeonSqlQueryA
Executes a read-only SQL query against your Neon database and returns the results.
Inputs: query (required).
executePostgreSQLSqlQueryA
Executes a read-only SQL query against your PostgreSQL database and returns the results.
Inputs: query (required).
executeSupabaseSqlQueryA
Executes a read-only SQL query against your Supabase database and returns the results.
Inputs: query (required).
fetchNeonSchemaA
Fetches the schema of the connected Neon database, showing tables and columns.
Inputs: no named parameters.
fetchPostgreSQLSchemaA
Fetches the schema of the connected PostgreSQL database, showing tables and columns.
Inputs: no named parameters.
fetchSupabaseSchemaA
Fetches the schema of the connected Supabase database, showing tables and columns.
Inputs: no named parameters.
getLinearFavoritesA
Retrieves a list of favorite projects and issues from Linear for the authenticated user.
Inputs: no named parameters.
getMiroBoardA
Retrieves detailed information about a specific Miro board including its items (sticky notes, shapes, etc.).
Inputs: boardId (required).
helloWayStationA
Call this action when users says 'Hello WayStation'. It displays welcome information about WayStation to the user
Inputs: no named parameters.
listAirtableBasesA
Returns a list of all Airtable bases the authenticated user has access to
Inputs: no named parameters.
listAirtableRecordsB
Retrieves records from the specified table with optional filtering and pagination
Inputs: baseId (required), tableId (required), sort, fields, +3 more.
listAirtableTablesA
Returns a list of all tables in the specified Airtable base
Inputs: baseId (required).
listAsanaFavoritesA
Retrieves a list of favorite projects and tasks from all workspaces associated with the authenticated user from Asana.
Inputs: no named parameters.
listAsanaProjectsB
Retrieves a list of projects associated with the specified Asana workspace.
Inputs: workspaceId (required).
listAsanaTasksC
Retrieves tasks from Asana filtered by project, assignee, and completion status.
Inputs: workspaceId (required), completed, projectId, assigneeId.
listAsanaWorkspacesA
Retrieves a list of workspaces associated with the authenticated user from Asana.
Inputs: no named parameters.
listGmailLabelsA
Retrieves a list of all labels in the user's Gmail account, including system labels like Inbox, Sent, Draft, and custom labels.
Inputs: no named parameters.
listGmailThreadsB
Retrieves a list of email threads/conversations from the user's Gmail account with optional filtering.
Inputs: query, labelIds, maxResults, includeSpamTrash.
listGoogleDocsA
Retrieves a list of Google Docs from the user's Drive, ordered by last modified date.
Inputs: no named parameters.
listJiraIssuesA
Retrieves a list of issues from a Jira project or using a JQL query.
Inputs: jql (required), maxResults.
listJiraProjectsA
Retrieves a list of projects accessible to the authenticated user from Jira.
Inputs: no named parameters.
listLinearIssuesC
Retrieves a list of issues from Linear.
Inputs: limit.
listLinearProjectsA
Retrieves a list of projects from Linear.
Inputs: no named parameters.
listLinearTeamsA
Retrieves a list of teams associated with the authenticated user from Linear.
Inputs: no named parameters.
listMiroBoardsA
Retrieves a list of boards associated with the authenticated user from Miro.
Inputs: no named parameters.
listMondayBoardsA
Retrieves a list of boards associated with the authenticated user from Monday.
Inputs: no named parameters.
listMyLinearIssuesA
Retrieves a list of issues assigned to the authenticated user in Linear.
Inputs: limit.
listNotionDatabasesA
Retrieves a list of databases the user has access to in Notion.
Inputs: no named parameters.
listNotionPagesB
Retrieves a list of pages the user has access to in Notion.
Inputs: no named parameters.
listOfficeDocsA
Retrieves a list of Office documents and folders from OneDrive, ordered by last modified date.
Inputs: folderId.
listSlackChannelsA
Retrieves a list of public and private channels from the authenticated user's Slack workspace.
Inputs: no named parameters.
listTeamsChannelsA
Retrieves a list of teams and channels from the authenticated user's Microsoft Teams workspace.
Inputs: no named parameters.
openWayStationA
Call this action when users says 'Open WayStation'. Opens the WayStation desktop application
Inputs: no named parameters.
postMiroNoteA
Adds a new sticky note with specified content to a Miro board at the given position.
Inputs: boardId (required), content (required), x, y, +1 more.
postSlackMessageA
Sends a text message to a specified Slack channel in the authenticated user's workspace.
Inputs: channel (required), message (required).
postTeamsMessageA
Sends a text message to a specified Microsoft Teams channel.
Inputs: teamId (required), message (required), channelId (required).
queryNotionDatabaseB
Retrieves and filters items from a specified Notion database.
Inputs: databaseId (required), sorts, filter, pageSize.
readAsanaProjectB
Retrieves all tasks from the specified Asana project. The tasks can be arbitrary JSON objects.
Inputs: projectId (required).
readAsanaTaskA
Retrieves detailed information about a specific Asana task by its ID.
Inputs: taskId (required).
readGmailThreadA
Retrieves a complete email thread/conversation with readable message content, stripped of unnecessary metadata.
Inputs: threadId (required), includeAttachments.
readGoogleDocA
Retrieves the content of a specific Google Doc as plain text.
Inputs: docId (required).
readJiraProjectA
Retrieves detailed information about a Jira project, including all available issue types with their IDs.
Inputs: projectIdOrKey (required).
readLinearIssueA
Retrieves comprehensive issue details including assignee, state, labels, comments, and related data from the specified Linear issue.
Inputs: issueId (required).
readLinearProjectA
Retrieves project metadata and all issues from the specified Linear project.
Inputs: projectId (required).
readMondayBoardA
Retrieves all items from the specified Monday board. The items can be arbitrary JSON objects.
Inputs: boardId (required).
readNotionPageB
Retrieves the content of a Notion page in the specified format.
Inputs: pageId (required), format.
readOfficeDocA
Retrieves the content of a specific Office document as text, converted from PDF.
Inputs: docId (required).
readSlackChannelA
Retrieves conversation history from a specified Slack channel, including thread replies.
Inputs: channel (required), limit, latest, oldest, +1 more.
recentOfficeDocsA
Retrieves a list of recently used Office documents by the user.
Inputs: no named parameters.
saveGmailDraftA
Creates and saves a draft email in the user's Gmail account that can be edited and sent later. Can optionally be created as a reply to an existing thread.
Inputs: to (required), body (required), subject (required), cc, +3 more.
searchAsanaTasksC
Searches for tasks in Asana that match the search term, with optional filtering by workspace, project, and completion status.
Inputs: query (required), workspaceId (required), projectId.
searchNotionC
Searches across a Notion workspace for pages, databases, and content matching the query.
Inputs: query (required), sort, filter.
searchOfficeDocsB
Searches for Office documents matching a specific query string.
Inputs: query (required).
sendGmailEmailA
Sends an email directly through the user's Gmail account. Can optionally be sent as a reply to an existing thread.
Inputs: to (required), body (required), subject (required), cc, +3 more.
updateAirtableRecordA
Updates the specified fields of an existing record in the given table
Inputs: baseId (required), fields (required), tableId (required), recordId (required).
updateAsanaTaskA
Updates an existing Asana task with new values for name, notes, due date, assignee, completion status, or custom fields.
Inputs: taskId (required), custom_fields (required), name, notes, +3 more.
updateJiraIssueC
Updates an existing issue in Jira with the provided details.
Inputs: issueKey (required), status, summary, assignee, +2 more.
updateLinearIssueB
Updates an existing issue in Linear with the specified changes.
Inputs: issueId (required), title, stateId, priority, +3 more.
updateMondayItemB
Updates an existing item in the specified Monday board with new column values. The column_values parameter is required and should always include the updated field(s) in { "column_id": "new_value" } format.
Inputs: item_id (required), board_id (required), column_values (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables seamless and secure connectivity between MCP hosts (like Claude Desktop, Cline, or Cursor) and productivity tools through WayStation's no-code integration hub.7166MIT
- AlicenseNot gradedqualityDmaintenanceProvides 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.MIT

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 infrastructure3-- 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