> ## Documentation Index
> Fetch the complete documentation index at: https://docs.molesignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect VS Code

> Connect VS Code and GitHub Copilot agent mode to MoleSignal Inbound MCP with mcp.json and OAuth.

VS Code supports remote HTTP MCP servers, OAuth authorization, resources, prompts, and tools.

## Configure the server

Create `.vscode/mcp.json` for a shared workspace configuration. For a private global
configuration, run **MCP: Open User Configuration** from the Command Palette.

```json theme={null}
{
  "servers": {
    "molesignal": {
      "type": "http",
      "url": "https://molesignal.example.com/api/v1/mcp"
    }
  }
}
```

<Steps>
  <Step title="Start the server">
    Open `mcp.json` and select the inline **Start** action, or run **MCP: List Servers** and choose
    `molesignal`.
  </Step>

  <Step title="Confirm trust">
    Review the endpoint and approve the MCP server trust prompt. A workspace configuration can be
    shared with every contributor, so keep credentials out of the file.
  </Step>

  <Step title="Complete OAuth">
    VS Code follows MoleSignal OAuth discovery and opens the browser authorization page. Complete
    the grant, then return to Chat agent mode.
  </Step>

  <Step title="Verify the connection">
    Run **MCP: List Servers**, inspect the `molesignal` status, and confirm the tools in the Chat
    view.
  </Step>
</Steps>

Use **Add Context → MCP Resources** to attach a MoleSignal resource, or invoke a published prompt
with `/molesignal.<prompt>`.

See the [official VS Code MCP documentation](https://code.visualstudio.com/docs/agent-customization/mcp-servers).