# VS Code

> Connect MCP Bond to VS Code with the Valency extension.

The Valency extension sets up MCP Bond in VS Code 1.109 or later.

## Quick setup

1. Open the [Valency extension in VS Code](vscode:extension/valencyio.valency). Allow the browser to open VS Code if prompted, then click **Install** inside VS Code. If it is already installed, skip this step. If the direct link does not open VS Code, use the [Marketplace page](https://marketplace.visualstudio.com/items?itemName=valencyio.valency).
2. Click **Sign in** in the Valency walkthrough or bottom-right notification and complete browser sign-in. If both prompts were dismissed, open the Command Palette with **Cmd+Shift+P** on macOS or **Ctrl+Shift+P** on Windows/Linux, then run **Valency: Sign in**. The bottom-right **Valency is connected** notification confirms sign-in worked; ignore the walkthrough if it still shows **Sign in**.
3. Open VS Code Chat in Agent mode and ask it to call Valency's `list_sources` tool. A returned source list confirms the connection.

## More about sign-in and verification

The **Get started with Valency** walkthrough normally opens on its **Sign in to Valency** step after installation, and a bottom-right notification offers another **Sign in** button. Both appear on installs and reinstalls, but not on updates. A Valency account is created automatically on first sign-in; its email does not have to match your GitHub or Microsoft email.

The bottom-right **Valency is connected** notification includes the number of research tools and an **Open Chat** button. It confirms sign-in worked; you can ignore the walkthrough if it still says **Sign in**. Ask an agent in VS Code Chat to call Valency's `list_sources` tool: a returned source list verifies that the agent can use it.

If an AI assistant helped install the extension and you completed browser sign-in yourself, return to that conversation and tell it sign-in is complete so it can make the verification call.

## Troubleshooting

**No Valency tools in Agent mode?** Run **Valency: Sign in** from the Command Palette. It starts the server, waits for tools, and reports the result. If it warns that the connection did not finish, choose **Show Output** to read the server log. **MCP: List Servers** shows whether Valency is running.

**The walkthrough didn't open?** Run **Welcome: Open Walkthrough...** from the Command Palette and choose **Get started with Valency**. VS Code skips its automatic opening when `workbench.welcomePage.walkthroughs.openOnInstall` is off.

**Need to switch accounts?** Sign out of Valency in the Accounts menu, then run **Valency: Sign in**.

**Extension won't install?** Check your VS Code version. The extension requires 1.109 or later. You can also install it with:

```bash
code --install-extension valencyio.valency
```

## Commands and uninstall

Open the Command Palette with **Cmd+Shift+P** on macOS or **Ctrl+Shift+P** on Windows/Linux.

| Command | What it does |
|---------|--------------|
| **Valency: Sign in** | Starts the Valency server interactively and opens browser sign-in if needed. |
| **Welcome: Open Walkthrough...** | Reopens the **Get started with Valency** walkthrough. |
| **MCP: List Servers** | Lists MCP servers, including Valency, with start, stop, and output actions. |
| **MCP: Show Output** | Opens the log for a server. |

The extension also has a **Valency** output channel under **View → Output**. To remove the extension, choose **Uninstall** from its gear menu in the Extensions view, or run `code --uninstall-extension valencyio.valency`. Sign-in state belongs to VS Code; sign out of Valency in the Accounts menu to clear it.

See [Troubleshooting](https://docs.valency.io/help/troubleshooting.md) for other connection issues or [report an issue](https://docs.valency.io/help/reporting-issues.md).