# VS Code

# Connect VS Code

VS Code's agent mode connects to remote MCP servers through an `mcp.json` file, or through a guided command.

New to Monad's MCP server? Start with the [MCP overview](/mcp/index).

## Prerequisites

- VS Code with GitHub Copilot and agent mode enabled
- A Monad account belonging to at least one organization
- MCP access enabled for your user — see [Access](/mcp/index#access)

## 1. Add the server

**Guided:** open the Command Palette and run **MCP: Add Server**, then follow the prompts, choosing **Global** to make Monad available everywhere or **Workspace** for this project only.

**By hand:** run **MCP: Open User Configuration** and add:

```json
{
  "servers": {
    "monad": {
      "type": "http",
      "url": "https://app.monad.com/mcp"
    }
  }
}
```

For a workspace-scoped server, put the same JSON in **`.vscode/mcp.json`**. That file can be committed to share the configuration with your team — each person still authenticates as themselves.

Note the shape differs from some other clients: VS Code uses `servers` (not `mcpServers`) and requires `"type": "http"` for a remote server.

## 2. Authorize

VS Code starts the server and runs the OAuth flow, opening your browser to Monad's consent screen. Approve it, and the tools become available in agent mode.

## 3. Verify

In the Chat view, switch to **Agent** mode and ask:

> List my Monad pipelines

You can also open the tools picker in the Chat view to confirm the Monad tools are listed.

## Next: Using It

You are connected. For what you can do through the MCP, example requests, and the habits that get good results, see **[Using the MCP](/guides/mcp-usage)**.

## Managing the Connection

Use **MCP: List Servers** to see status, start/stop the server, and view its logs — the logs are the quickest way to see why a connection failed.

To disconnect properly, revoke the client under **Settings → Connected Applications** in the Monad UI, then remove the entry from your `mcp.json`.

## Troubleshooting

**The server does not start.**
Run **MCP: List Servers**, select Monad, and open its output log. Configuration errors and failed authorization both show up there.

**Monad's tools do not appear in chat.**
Confirm you are in **Agent** mode rather than Ask mode, and check the tools picker — tool sets can be toggled off per conversation.

**The config is ignored.**
Check you used `servers` rather than `mcpServers`, and included `"type": "http"`. VS Code's schema differs from Cursor's and Claude's.

For anything not specific to VS Code — refused requests, missing organizations, writes being denied — see [Troubleshooting](/mcp/index#troubleshooting) on the overview page.