meto
VS Code

VS Code

Extension Ready

MCP Context for Cline, Roo Code, and Continue in Visual Studio Code

Connect in Meto
The Challenge Without Meto

Autonomous coding extensions in VS Code make incorrect assumptions about package versions or create unneeded boilerplate without explicit architectural constraints.

The Meto Solution

Meto provides a unified MCP server that Cline, Roo Code, and Continue query during task execution, ensuring all generated files adhere to your tech stack.

Key Advantages with VS Code

Unified context across Cline, Roo Code, and Continue extensions
Works with local open-source models (Ollama) and cloud LLMs
Enforces strict typing, linting, and folder structure conventions
Zero maintenance across multiple VS Code workspace windows

Step-by-Step Configuration Guide

1

Open Extension MCP Settings

In VS Code, open your extension panel (Cline or Continue). Click the MCP servers tab (or open cline_mcp_settings.json).

2

Paste Configuration

Add Meto under the 'mcpServers' configuration object.

cline_mcp_settings.json
{
  "mcpServers": {
    "meto": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.metoctx.com/api/mcp/your-username",
        "--header",
        "Authorization: Bearer meto_mcp_your_personal_token"
      ]
    }
  }
}

Frequently Asked Questions

Does this work on VS Code Remote SSH / Dev Containers?

Yes. Because Meto runs over standard npx mcp-remote, it works in local, remote SSH, WSL2, and Docker dev container environments.

Ready to give VS Code persistent memory?

Create your Meto profile in 2 minutes. Fill in your stack once, and never repeat your setup again.

Get Started for FreeAll Integrations