Quickstart: Cline

Cline (the VS Code agent extension) connects to MCP servers via its built-in MCP marketplace or a settings panel.

Via marketplace (when listed)

Pipeworx is submitted to the Cline MCP Marketplace (issue #1525). Once approved, search “Pipeworx” in Cline’s MCP marketplace pane and click Install.

Manual install (works today)

  1. In VS Code, open the Cline sidebar
  2. Click the MCP Servers icon (or open Cline Settings → MCP)
  3. Click Edit MCP Servers
  4. Add this entry:
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
  1. Save. Cline reconnects automatically.

Verify

In a Cline chat, ask:

What’s the FDA adverse event count for Ozempic?

Cline picks ask_pipeworx (which routes to fda_drug_events) and returns the count.

Cline-specific tips

Auto-approval. Cline’s “auto-approve tool calls” setting can be toggled per-server. For Pipeworx, auto-approving read-only data tools is safe (no destructive operations exist in the catalog).

Tool browser. Cline’s MCP pane has a built-in tool browser. Useful for discovering Pipeworx’s tool surface — but recommend using discover_tools(task) instead, which is task-aware and faster.

Long sessions. Cline keeps tool definitions in context across turns. For long sessions, scope by task to keep context tax low:

{
  "mcpServers": {
    "pipeworx-finance": {
      "url": "https://gateway.pipeworx.io/mcp?task=sec+filings+financial"
    }
  }
}

Troubleshooting

“Could not connect to server.” Cline expects either a URL (url) or stdio command (command + args). For Pipeworx use the URL form.

Tool list looks short. That’s expected — the default gateway URL exposes ~20 most-relevant + 5 meta-tools. Use discover_tools to expand mid-session.

Last reviewed May 8, 2026