---
title: "VS Code MCP Setup: Add ToolPiper with Cline or Continue on Mac"
description: "Connect VS Code to ToolPiper's local MCP server through Cline or Continue. Over 300 local tools available inside VS Code agent sessions."
date: 2026-05-15
author: "Ben Racicot"
tags: ["VS Code", "Cline", "Continue", "MCP", "Model Context Protocol", "Setup Guide", "macOS"]
type: "article"
canonical: "https://modelpiper.com/blog/vscode-cline-continue-mcp-toolpiper/"
---

# VS Code MCP Setup: Add ToolPiper with Cline or Continue on Mac

> Connect VS Code to ToolPiper's local MCP server through Cline or Continue. Over 300 local tools available inside VS Code agent sessions.

## TL;DR

VS Code doesn't have native MCP support yet. The route in is through an MCP-capable extension. Cline (formerly Claude Dev) supports MCP servers directly through its settings. Continue supports MCP through its config.json. Both can register ToolPiper at http://127.0.0.1:9998/mcp.

VS Code doesn't have native MCP support. To use MCP servers from VS Code, you need an extension that adds the capability. Cline and Continue are the two most established. Both treat MCP as a first-class extension point and both work with ToolPiper.

## Which VS Code extension should I use?

Cline if you want an agent that takes broad action across your codebase and your Mac (browser, system, files) in a single task. Continue if you want a more conservative chat-and-suggest experience with manual tool approval. Both support MCP servers. ToolPiper plugs into either.

Quick comparison. Cline is the autonomous agent of the two. It plans multi-step tasks and calls tools without per-step approval (configurable), with MCP as a core integration point and settings in `.cline_mcp_settings.json`. Continue takes the chat-first approach, organized around slash commands and context providers, with MCP support added in newer versions and settings in `~/.continue/config.json`.

VS Code Copilot has its own MCP roadmap. As of this writing it doesn't support arbitrary MCP servers in the same way Cline and Continue do. If Copilot is your only VS Code AI, you'll need to wait for native support or use one of the other extensions alongside it.

## How do I add ToolPiper to Cline?

Open Cline's MCP settings (extension settings -> MCP Servers). Add a new server with name "toolpiper", type "http", and URL "http://127.0.0.1:9998/mcp". Save. Cline reloads the MCP catalog automatically.

If Cline's UI doesn't offer the option to add HTTP MCP servers, edit the underlying settings file directly. The file is at `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json` on macOS. Add a `toolpiper` entry to `mcpServers`:

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

Restart Cline by reloading the VS Code window (Cmd-Shift-P -> "Developer: Reload Window"). The next chat session sees ToolPiper's tools.

## How do I add ToolPiper to Continue?

Edit `~/.continue/config.json`. Add a `mcpServers` array with a ToolPiper entry. Reload the VS Code window or restart VS Code. Continue picks up the new server on next start.

```
{
  "mcpServers": [
    {
      "name": "toolpiper",
      "type": "http",
      "url": "http://127.0.0.1:9998/mcp"
    }
  ]
}
```

Continue's config file may already exist with other settings. Add the `mcpServers` field at the top level alongside `models`, `contextProviders`, and others. If `mcpServers` exists, append your ToolPiper entry to the array.

## How do I verify the connection?

In Cline, the MCP settings UI shows each registered server's status. `toolpiper` should show as Connected. In Continue, the slash command palette lists MCP tools when you type /. Either way, ask the agent to call a ToolPiper tool to confirm end-to-end.

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

> _"Take a screenshot of my screen and describe what's on it."_

If the agent invokes `vision_screenshot` + `vision_ocr` (or describes the screen directly from the screenshot), the connection works. If the agent says it can't take screenshots, the registration didn't take. Re-check the settings file or extension status.

## What if VS Code's extension can't see ToolPiper?

Three checks. ToolPiper is running. The extension's MCP config is valid. You reloaded the VS Code window. Extension-specific status indicators reveal which one failed.

1.  ToolPiper running. `curl http://127.0.0.1:9998/health` from Terminal. JSON response means alive.
2.  Config valid. Whichever extension you're using, the settings file is JSON. Validate it. A trailing comma can kill the entire registration silently.
3.  VS Code reloaded. Cmd-Shift-P -> "Developer: Reload Window". Extensions read MCP config at activation time, not on file change.

For Cline, the MCP settings UI shows per-server connection status with diagnostic messages. For Continue, the developer tools console (Help -> Toggle Developer Tools) shows MCP discovery errors with stack traces.

## Does this work for VS Code Copilot or Cursor's VS Code fork?

VS Code Copilot doesn't support arbitrary MCP servers yet, so ToolPiper can't plug in through Copilot directly. Cursor is a separate VS Code fork with its own MCP system, covered in the dedicated Cursor guide.

If Copilot is your primary VS Code AI, install Cline or Continue alongside it. The extensions don't conflict, and you get ToolPiper's tools through the MCP-aware extension while keeping Copilot for inline suggestions.

For full MCP setup options across other editors, see [MCP Setup on Mac](/blog/mcp-setup-guide-mac).

## FAQ

### Where is Cline's MCP settings file?

On macOS: `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`. The exact path depends on your VS Code variant (regular, Insiders, etc.). Cline's MCP settings UI is the safer way to find it.

### Where is Continue's config file?

`~/.continue/config.json`. The same file holds your model list, context providers, and slash commands. MCP servers go under a top-level `mcpServers` array.

### Does VS Code Copilot support MCP?

Not for arbitrary user-registered MCP servers as of this writing. Microsoft has been moving in that direction but the public-facing API hasn't shipped. Use Cline or Continue for MCP support in the meantime.

### Can I run Cline and Continue together with the same ToolPiper?

Yes. ToolPiper handles multiple MCP clients concurrently. Cline and Continue each register independently, each makes their own tool discovery, and both see the same over 300 tools.

### Do I need to restart VS Code for MCP config changes?

A window reload (Cmd-Shift-P -> "Developer: Reload Window") is usually enough. Some extension state survives reloads, so a full quit and relaunch is the surer path if a reload doesn't pick up the change.