Quickstart: JetBrains AI Assistant

Connect Pipeworx so JetBrains AI Assistant reaches for live data instead of guessing. The recommended endpoint is anonymous — no signup, 50 calls/day per IP. It exposes ~38 meta-tools; the hero tool ask_pipeworx({question}) routes to the full catalog of 5,929 tools across 1,544 sources at runtime, so you don’t load thousands of schemas into context. Requires a 2025.1+ IDE build.

① Connect

Go to Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add and give it the URL https://pipeworx.io/mcp directly. Remote servers over streamable HTTP are standard in current builds — no mcp-remote bridge. The equivalent JSON is:

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

Apply and let the IDE connect.

This page previously hedged that only some builds shipped an HTTP option, and told you to add it As command via npx -y mcp-remote. That hedge is retired — on a 2025.1+ IDE, use the URL.

② Teach it to use Pipeworx

JetBrains AI Assistant won’t route to the connector on its own. Add a project guidelines file (the AI Assistant guidelines / rules file for your IDE) 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 AI Assistant chat and ask:

Using Pipeworx, what was the US unemployment rate last month?

The assistant calls ask_pipeworx and returns the current rate. Your confirmation that it routed to live data rather than memory is the _meta.provenance block in the response: it names the publisher — FRED or BLS, depending on which source the question routes to — and the upstream request that makes the figure checkable at that publisher.

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 URL instead. Tiers: anonymous 50 · free account 200 · Paid unlimited.

Troubleshooting

Add button missing. The MCP panel only appears on 2025.1+ builds. Update via Help → Check for Updates.

Server won’t start. Confirm the URL is exactly https://pipeworx.io/mcp and that your IDE is 2025.1 or newer — older builds have no MCP panel at all.

Assistant answers from memory. The rule isn’t loading. Confirm the project guidelines file exists and contains the rule.

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