# VS Code

VS Code can connect to Memside through MCP when GitHub Copilot Chat and MCP
servers are enabled. The connection lets compatible agent tools read selected
Memories, checkpoints, Operating Rules, and other saved project context.

Memside is currently configured manually because it is not listed in the VS
Code MCP gallery.

## Before starting

The setup requires:

- a current VS Code version with MCP support;
- GitHub Copilot Chat when Memside will be used through Copilot;
- a Memside API key from **Settings > Developer & API**.

## Option 1: Make Memside available across projects

Use the user configuration when the same Memside connection should be available
in every VS Code workspace.

1. Open the Command Palette.
2. Run **MCP: Open User Configuration**.
3. Add the configuration shown below to the opened `mcp.json` file.
4. Save the file.
5. Enter the Memside API key when VS Code requests it.
6. Approve the server if VS Code asks whether it is trusted.

## Option 2: Add Memside to one workspace

Use this option when Memside should be available only in one project.

1. Open the project in VS Code.
2. Create or open `.vscode/mcp.json`.
3. Add the following configuration. The same configuration is used for the
   user-level setup above.

```json
{
  "inputs": [
    {
      "type": "promptString",
      "id": "memside-api-key",
      "description": "Memside API key",
      "password": true
    }
  ],
  "servers": {
    "memside": {
      "type": "http",
      "url": "https://api.memside.com/mcp/",
      "headers": {
        "Authorization": "Bearer ${input:memside-api-key}"
      }
    }
  }
}
```

4. Save the file.
5. Enter the Memside API key when VS Code requests it.
6. Approve the server if VS Code asks whether it is trusted.
7. Open Copilot Chat in Agent mode.

The password input keeps the API key out of the workspace file. A shared
`.vscode/mcp.json` file must never contain a real key.

## Confirm the connection

1. Run **MCP: List Servers**.
2. Select `memside`.
3. Start or restart the server.
4. Confirm that it shows as running.
5. Confirm that tools were discovered.

Then run a read-only test in Copilot Chat:

```text
Use Memside to find the active project checkpoint before starting work.
```

## Troubleshooting

- Update VS Code and the GitHub Copilot extension.
- Confirm that the workspace is trusted.
- Run **MCP: List Servers** and restart `memside`.
- Check whether an organization policy restricts MCP servers.
- Recreate the Memside API key if authentication continues to fail.

## Next steps

- [GitHub Copilot](/connect/github-copilot/)
- [API keys](/developers/api-keys/)
- [Troubleshooting](/help/troubleshooting/)