Menu

VS Code Setup

Connect a paso MCP server to VS Code.

Set up paso as an MCP server in VS Code.

Requires VS Code 1.99+ with the GitHub Copilot extension. MCP support is part of Copilot’s agent mode.

1. Install paso

npm install -g usepaso

Or use it locally with npx.

2. Connect

Run this from the directory containing your usepaso.yaml:

usepaso connect vscode
Added "Sentry" in VS Code config.
  Config: .vscode/mcp.json

Reload VS Code to connect.

paso writes .vscode/mcp.json in your project root. VS Code uses servers instead of mcpServers. Different key, same idea. usepaso connect handles this.

To remove the server later: usepaso disconnect vscode.

3. Reload VS Code

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run Developer: Reload Window. Or close and reopen VS Code.

Verify Setup

Open Copilot Chat and switch to agent mode. Your paso capabilities appear as available tools. Try calling one to verify.

Multiple Servers

Run usepaso connect vscode from each service’s project directory. paso adds each entry to the same .vscode/mcp.json.

# In /path/to/sentry/
usepaso connect vscode

# In /path/to/github/
usepaso connect vscode

To remove a server: run usepaso disconnect vscode from that service’s directory.

Troubleshooting

Server doesn’t appear in Copilot. Check that Copilot is running in agent mode. Reload the VS Code window. Run usepaso validate to confirm the declaration is valid.

“command not found”. Use npx usepaso serve (no global install needed).

Auth failures (401). Set USEPASO_AUTH_TOKEN in your shell or in a .env file next to your usepaso.yaml. Run usepaso doctor to check your setup end-to-end.

Server crashes on start. Run usepaso serve directly in a terminal to see the error output. Run usepaso validate to check for declaration errors.

VS Code can now reach your API.

Your capabilities are live in Copilot agent mode. Try calling one in a chat.

Next, you might want to: