Skip to main content
Glama
pipeworx-io

mcp-monday

by pipeworx-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mcp-monday

Monday.com MCP — wraps the Monday.com GraphQL API (BYO API key)

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool

Description

monday_list_boards

List all boards in your account. Returns board ID, name, state, and item count to discover available boards.

monday_get_board

Get board structure and metadata (e.g., board ID "12345"). Returns name, columns, groups, and item count.

monday_list_items

List items in a board (e.g., board ID "12345"). Returns item ID, name, group, column values, and created date.

monday_create_item

Create a new item in a board (e.g., board ID "12345", name "New Task"). Returns created item ID and name.

monday_search_items

Search for items across all boards by keyword. Returns matching items with ID, name, board name, and column values.

Related MCP server: @morphixai/mcp-server

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "monday": {
      "url": "https://gateway.pipeworx.io/monday/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/monday/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Monday data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • pontal-mcp

    mtrajano
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    Remote MCP server exposing Monday.com tools for leads and work namespaces via streamable HTTP, enabling Claude agents to list leads/jobs and get updates.
    -

  • MCP Moloni ON

    rubencodex86
    F
    license
    Not graded
    quality
    B
    maintenance
    MCP server that exposes the Moloni ON GraphQL API to AI clients, providing a curated set of operations as typed and documented tools.
    -