Pipeworx Catalog

Pipeworx Catalog MCP — Exposes the full Pipeworx platform to Claude

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "pipeworx-catalog": {
      "command": "npx",
      "args": [
        "-y",
        "pipeworx-catalog"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

mcp-pipeworx-catalog

Pipeworx Catalog MCP — Exposes the full Pipeworx platform to Claude

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

Tools

Tool	Description
`list_packs`	Browse all available Pipeworx packs. Returns pack names, categories, tool counts, and gateway URLs. Use to discover data sources or explore what's available.
`get_pack_tools`	Get tool definitions for a specific pack (e.g., 'weather', 'stocks'). Returns tool names, descriptions, parameters, and requirements. Use before calling a tool to verify its interface.
`get_connection_config`	Get MCP setup instructions for connecting to Pipeworx packs. Returns connection details and gateway URLs. Use to configure your environment.
`search_packs`	Search packs by keyword across names, descriptions, and tools (e.g., 'weather', 'translate'). Returns matching packs with details. Use to find specific capabilities.
`get_platform_status`	Check Pipeworx platform health and availability. Returns pack count, active tool count, and any service alerts. Use to verify system status before operations.
`search_mcp_directory`	Search thousands of MCP servers by use case (e.g., 'database', 'email', 'calendar'). Returns community and hosted servers. Use to find tools beyond Pipeworx.
`data_freshness`	MEASURES publication lag for a curated set of high-value live-data sources — how fresh is this data, how old is this number, is this feed real-time, what's the data staleness on X. Every entry is PROBED LIVE against its upstream (not read from a hardcoded table): fetches the newest available datapoint right now and reports the observed lag between that datapoint and this moment. Use before pricing or settling off a number ("can I trust this PortWatch chokepoint count as current", "how stale is Polymarket vs Kalshi order flow", "when did BLS last publish CPI"). Covers maritime chokepoint traffic (IMF PortWatch), vessel AIS positions (Digitraffic), prediction-market trade tape (Polymarket, Kalshi), global news event ingestion (GDELT), and US CPI (BLS) — pass `source` (forgiving match, e.g. "portwatch", "digitraffic ais", "polymarket", "kalshi", "gdelt", "cpi") or `category` ("maritime", "markets", "news", "economics") to scope the probe, or omit both to probe every curated source. Lag is measured at call time and can vary between calls — this tool never reports a lag it did not just observe.

Quick Start

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

config.json

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/pipeworx-catalog/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:

config.json

{
  "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:

Code

ask_pipeworx({ question: "your question about Pipeworx Catalog data" })

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

License

MIT

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Pipeworx Catalog

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "pipeworx-catalog": { "command": "npx", "args": ["-y", "Pipeworx Catalog"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Pipeworx Catalog AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/pipeworx-catalog?style=directory)](https://allmcps.com/mcp/pipeworx-catalog)

HTML Embed

<a href="https://allmcps.com/mcp/pipeworx-catalog"><img src="https://allmcps.com/api/badge/pipeworx-catalog?style=directory" alt="Pipeworx Catalog on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Pipeworx Catalog →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

mcp-pipeworx-catalog

Pipeworx Catalog MCP — Exposes the full Pipeworx platform to Claude

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

Tools

Tool	Description
`list_packs`	Browse all available Pipeworx packs. Returns pack names, categories, tool counts, and gateway URLs. Use to discover data sources or explore what's available.
`get_pack_tools`	Get tool definitions for a specific pack (e.g., 'weather', 'stocks'). Returns tool names, descriptions, parameters, and requirements. Use before calling a tool to verify its interface.
`get_connection_config`	Get MCP setup instructions for connecting to Pipeworx packs. Returns connection details and gateway URLs. Use to configure your environment.
`search_packs`	Search packs by keyword across names, descriptions, and tools (e.g., 'weather', 'translate'). Returns matching packs with details. Use to find specific capabilities.
`get_platform_status`	Check Pipeworx platform health and availability. Returns pack count, active tool count, and any service alerts. Use to verify system status before operations.
`search_mcp_directory`	Search thousands of MCP servers by use case (e.g., 'database', 'email', 'calendar'). Returns community and hosted servers. Use to find tools beyond Pipeworx.
`data_freshness`	MEASURES publication lag for a curated set of high-value live-data sources — how fresh is this data, how old is this number, is this feed real-time, what's the data staleness on X. Every entry is PROBED LIVE against its upstream (not read from a hardcoded table): fetches the newest available datapoint right now and reports the observed lag between that datapoint and this moment. Use before pricing or settling off a number ("can I trust this PortWatch chokepoint count as current", "how stale is Polymarket vs Kalshi order flow", "when did BLS last publish CPI"). Covers maritime chokepoint traffic (IMF PortWatch), vessel AIS positions (Digitraffic), prediction-market trade tape (Polymarket, Kalshi), global news event ingestion (GDELT), and US CPI (BLS) — pass `source` (forgiving match, e.g. "portwatch", "digitraffic ais", "polymarket", "kalshi", "gdelt", "cpi") or `category` ("maritime", "markets", "news", "economics") to scope the probe, or omit both to probe every curated source. Lag is measured at call time and can vary between calls — this tool never reports a lag it did not just observe.

Quick Start

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

config.json

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

What this endpoint actually serves

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

config.json

{
  "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:

Code

ask_pipeworx({ question: "your question about Pipeworx Catalog data" })

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

License

MIT