Pipeworx Docs

Pipeworx is an MCP gateway that gives AI agents one URL to live, primary-source data: SEC filings, FDA records, FRED economic series, ATTOM property data, ClinicalTrials.gov, RxNorm, USPTO, and 280+ more sources. 1,007 tools across 295 packs — but agents only ever see the ~20 most relevant per session.

60-second quickstart

Add this to any MCP client config:

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

Then ask the agent something:

“What is the US trade deficit with China?” “Get Apple’s latest 10-K filing.” “What are the side effects of Ozempic?”

The gateway picks the right tool, fills the arguments, executes, and returns the answer. No API keys for the free tier. No setup.

What’s different

• Full MCP protocol. Most servers ship Tools and stop. Pipeworx ships Tools + Resources + Prompts, the way the spec was designed.
• No context tax. Connect to the gateway once; agents see ~20 tools at a time via on-demand discovery. They never carry 1,000 tool definitions in the context window.
• Meta-tools that collapse multi-call patterns. compare_entities({type:"drug", values:["ozempic","mounjaro"]}) returns adverse events, approvals, and trial counts in one parallel call instead of eight sequential ones.
• Citations as first-class. Every entity has a pipeworx:// URI agents can embed in output for stable references.
• Authoritative sources. SEC, FDA, FRED, Census, EPA, ATTOM, ClinicalTrials.gov — primary sources, no scraped web data.

Where to go next

• New here? Quickstart for your client
• Building an agent? Recipes — copy-paste workflows for common tasks
• Want to understand the design? Concepts — the four ideas that make Pipeworx different
• Looking up a specific tool? API Reference — every pack, every tool

Tiers

When something’s wrong

Every tool error response carries _meta.examples, _meta.alternatives, and a _meta.feedback_hint. Agents can self-correct on retry; humans can file via pipeworx_feedback. The Pipeworx team reviews feedback daily.