Skip to main content
VS Code supports stdio and remote HTTP MCP servers, OAuth authorization, resources, prompts, and tools. The client starts the MoleSignal CLI, which carries the messages to MoleSignal. It needs Node.js 20 or later.
1

Sign in once

The browser opens on MoleSignal to approve the sign-in; the CLI keeps it and renews it.
2

Add MoleSignal

In .vscode/mcp.json:
Start the server from the file or the MCP view, and approve the trust prompt.
Where no browser is at hand, set MOLESIGNAL_URL and MOLESIGNAL_TOKEN (an API token) in the server’s environment instead of signing in. See Connect over stdio. The sections below connect over Streamable HTTP, without the CLI.

​
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.
1

Start the server

Open mcp.json and select the inline Start action, or run MCP: List Servers and choose molesignal.
2

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.
3

Complete OAuth

VS Code follows MoleSignal OAuth discovery and opens the browser authorization page. Complete the grant, then return to Chat agent mode.
4

Verify the connection

Run MCP: List Servers, inspect the molesignal status, and confirm the tools in the Chat view.
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.
Last modified on October 18, 2026