Quickstart: Continue.dev

Connect Pipeworx so Continue 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

Add Pipeworx to ~/.continue/config.yaml:

mcpServers:
  - name: pipeworx
    type: streamable-http
    url: https://pipeworx.io/mcp

Save the file. Continue reloads the config automatically; open the agent panel and confirm Pipeworx is listed.

② Teach it to use Pipeworx

Continue won’t route to the connector on its own. Add a Continue rules block 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 Continue agent panel and ask:

What was the US unemployment rate last month?

Continue 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:

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

For Sign in (200/day), set url: https://gateway.pipeworx.io/oauth/mcp instead. Tiers: anonymous 50 · free account 200 · Paid unlimited.

Troubleshooting

Server not listed. Check YAML indentation — mcpServers is a top-level key and each server is a list item under it. Tabs break YAML; use spaces.

Connection fails. Confirm type: streamable-http is spelled exactly and the URL has no trailing whitespace.

Continue answers from memory. The rule isn’t loading. Confirm the rules block is present in your config and the agent is using a model that supports tool calls.

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