New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

@pipeworx/mcp-monday

Package Overview
Dependencies
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@pipeworx/mcp-monday

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

latest
Source
npmnpm
Version
0.2.1
Version published
Weekly downloads
0
Maintainers
1
Weekly downloads
 
Created
Source

mcp-monday

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

Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
monday_list_boardsList all boards in your account. Returns board ID, name, state, and item count to discover available boards.
monday_get_boardGet board structure and metadata (e.g., board ID "12345"). Returns name, columns, groups, and item count.
monday_list_itemsList items in a board (e.g., board ID "12345"). Returns item ID, name, group, column values, and created date.
monday_create_itemCreate a new item in a board (e.g., board ID "12345", name "New Task"). Returns created item ID and name.
monday_search_itemsSearch for items across all boards by keyword. Returns matching items with ID, name, board name, and column values.

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 1865+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/monday_list_boards. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-monday is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/monday/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "monday": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-monday"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

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

Keywords

mcp

FAQs

Package last updated on 03 Nov 2026

Related posts