Lovie MCP›VS Code

Editor

VS Code

VS Code ships MCP support in Copilot's agent mode. Its config key is servers, not mcpServers — the single most common reason a pasted snippet does nothing here.

The only value you need

• Time 1 minute
• Transport HTTP streamable
• Auth OAuth — in-app
• Config mcp.json

One click

Add Lovie to VS Code

VS Code asks you to confirm the server before it starts it.

Or through the Command Palette

1. Press ⇧⌘P (macOS) or Ctrl + Shift + P, and run MCP: Add Server.
2. Choose the HTTP option — the one described as HTTP or Server-Sent Events.
3. Paste https://mcp.lovie.co/mcp.
4. Give it the server ID lovie.
5. Choose where it lives: Global writes your user mcp.json, Workspace writes .vscode/mcp.json in the project.
6. VS Code starts the server and asks you to sign in. Approve in the browser; the token is kept in VS Code’s account store.

Or write the file

.vscode/mcp.json in the project, or the user file from MCP: Open User Configuration:

{
  "servers": {
    "lovie": {
      "type": "http",
      "url": "https://mcp.lovie.co/mcp"
    }
  }
}

Use it

1. Open Chat with ⌃⌘I (macOS) or Ctrl + Alt + I, and switch to Agent mode.
2. Click Configure Tools and tick the Lovie tools you want available.
3. Ask for something. VS Code prompts before the first run of each tool.

Managing it later

Where	What you get
Extensions view	The MCP SERVERS — INSTALLED section: start, stop, restart, view logs
MCP: List Servers	The same actions from the Command Palette
Chat → Configure Tools	Which tools this chat may call

If something goes wrong

Symptom	Cause
Server not listed after editing the file	You wrote mcpServers instead of servers.
Listed but never called	Chat is in Ask or Edit mode. Only Agent mode calls tools.
Too many tools to pick from	Untick everything you do not need under Configure Tools; the model picks better from a shorter list.
Sign-in never completes	Restart the server from the Extensions view. It re-runs the authorization from a clean state.

Somewhere else