VS Code has native MCP support: GitHub Copilot's agent mode in VS Code can call tools from any MCP server you register in an mcp.json file. That is the simplest way in. Cline and Continue are MCP-capable extensions that work too, if you already use one of them.

How do I add ToolPiper to VS Code?

Run MCP: Open User Configuration from the Command Palette (Cmd-Shift-P) to open your user-level mcp.json, or create .vscode/mcp.json in a project. Add a toolpiper server with type set to http and the URL http://127.0.0.1:9998/mcp. MCP: Add Server in the Command Palette walks through the same thing.

{
  "servers": {
    "toolpiper": {
      "type": "http",
      "url": "http://127.0.0.1:9998/mcp"
    }
  }
}

Then open the chat view in agent mode. ToolPiper's tools appear under the Configure Tools button in the chat input, where you can turn individual tools off. The file format and the current options are in VS Code's MCP documentation.

Should I use Cline or Continue instead?

Only if you already use one of them. Cline is the autonomous agent of the two: it plans multi-step tasks and calls tools without per-step approval (configurable). Continue takes a chat-first approach. Both register MCP servers in their own config, and both work with ToolPiper at the same URL.

How do I add ToolPiper to Cline?

In the Cline panel, click the MCP Servers icon, open the Configure tab and click Configure MCP Servers. Add a toolpiper entry with type set to streamableHttp and the URL http://127.0.0.1:9998/mcp. Leaving type out makes Cline use the legacy SSE transport, which is the wrong one for ToolPiper.

The settings file is ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json on macOS:

{
  "mcpServers": {
    "toolpiper": {
      "type": "streamableHttp",
      "url": "http://127.0.0.1:9998/mcp"
    }
  }
}

The format is documented in Cline's MCP guide.

How do I add ToolPiper to Continue?

Add an mcpServers entry to Continue's YAML config, ~/.continue/config.yaml, or put it in its own file under .continue/mcpServers/ in your workspace. Use type: streamable-http and the ToolPiper URL. Continue's older config.json is deprecated.

mcpServers:
  - name: toolpiper
    type: streamable-http
    url: http://127.0.0.1:9998/mcp

If config.yaml already has an mcpServers list, add the ToolPiper entry to it. The format is in Continue's MCP documentation.

How do I verify the connection?

In VS Code, ToolPiper's tools show under Configure Tools in the chat input. In Cline, the MCP Servers view shows each registered server's status. Either way, ask the agent to call a free ToolPiper tool to confirm end-to-end.

Test prompt that's likely to trigger a free tool:

"Check ToolPiper's system status and tell me which models are loaded."

If the agent calls system_status and reports back, the connection works. If it says it has no such tool, the registration didn't take. Re-check the config file and the server status.

Is there a token to configure?

No. VS Code, Cline and Continue talk to ToolPiper over loopback, and ToolPiper trusts loopback connections at the socket level. It mints a short-lived bearer token at ~/Library/Application Support/ToolPiper/.toolpiper-token (mode 0600, rotated every launch) so local clients just work with nothing to paste into your VS Code settings.

That ambient trust stops at the machine boundary. Reach ToolPiper from a LAN device or a PiperMesh peer and you have to present a scoped Bearer tp_<64 hex> token with the right audience, never written into any config you don't control. Inside ToolPiper, the Connected Apps pane lists every authenticated client as a labeled row showing its tool-access state, with one-click revoke that kills the bearer immediately and leaves the row visible as revoked. A restrict-only tool-governance overlay lets you deny specific tools (say system_run_command) for every client or swap the tool marketplace from open browse to an explicit allow-list. It only narrows what a tier already permits. Today that overlay is per-device and edited locally; the same policy shape is built so an organization can push it later, at which point the controls lock behind a "Managed by your organization" badge.

What if VS Code can't see ToolPiper?

Three checks. ToolPiper is running. The MCP config is valid. The server is started. Each status indicator reveals which one failed.

  1. ToolPiper running. curl http://127.0.0.1:9998/health from Terminal. JSON response means alive.
  2. Config valid. The file is JSON (or YAML for Continue). A trailing comma or bad indentation can kill the whole registration.
  3. Server started. In VS Code, run MCP: List Servers and start or restart toolpiper. For the extensions, reload the window (Cmd-Shift-P -> "Developer: Reload Window").

If ToolPiper was not running when VS Code first tried to connect, start ToolPiper and restart the server from the same list.

Does this work for Cursor?

Cursor is a separate VS Code fork with its own MCP system, covered in the dedicated Cursor guide.

For full MCP setup options across other editors, see MCP Setup on Mac.