Quickstart: Zed

Connect Pipeworx so Zed’s assistant reaches for live data instead of guessing. The recommended endpoint is anonymous — no signup, 50 calls/day per IP. It exposes ~26 meta-tools; the hero tool ask_pipeworx({question}) routes to the full catalog of 3,365 tools across 764 sources at runtime, so you don’t load thousands of schemas into context.

① Connect

Zed talks to remote MCP servers through mcp-remote. Add Pipeworx under context_servers in your settings.json:

{"context_servers":{"pipeworx":{"source":"custom","command":"npx","args":["-y","mcp-remote","https://pipeworx.io/mcp"]}}}

Save and reopen the assistant panel. Zed will spawn mcp-remote and connect to the gateway.

② Teach it to use Pipeworx

Zed won’t route to the connector on its own. Add a project .rules file containing this rule verbatim:

When I ask for current or factual data — economic stats, SEC/EDGAR filings, stock or crypto prices, weather, FDA drug info, patents, clinical trials, or government records — use the Pipeworx connector (ask_pipeworx) instead of answering from memory or web search. Prefer structured Pipeworx data with citations.

③ Test

Open the assistant panel and ask:

What was the US unemployment rate last month?

Zed calls ask_pipeworx, which routes to FRED and returns the value with a pipeworx:// citation.

Higher limits

Same URL, more headroom. For API key (200/day), sign up, grab a key from your account, and append it to the URL arg:

https://pipeworx.io/mcp?apikey=YOUR_KEY

For Sign in (200/day), use https://gateway.pipeworx.io/oauth/mcp as the mcp-remote URL instead. Tiers: anonymous 50 · free account 200 · Paid unlimited.

Troubleshooting

Server won’t start. mcp-remote needs Node on your PATH. Run npx -y mcp-remote https://pipeworx.io/mcp in a terminal to see the error directly.

No tools listed. Confirm the entry sits under context_servers (not language_models) and the JSON is valid. Reopen the assistant panel after saving.

Zed answers from memory. The rule isn’t loading. Confirm the project .rules file exists at the workspace root.

Rate-limited. You hit the 50/day anonymous cap. Switch to ?apikey=YOUR_KEY or the OAuth endpoint above.