VS Code

Connect

1. Click Add to VS Code below and press Install in VS Code. To add it by hand instead, run MCP: Open User Configuration from the Command Palette and add the server to servers.

Add to VS Code

// mcp.json
{
  "servers": {
    "laterbase": {
      "type": "http",
      "url": "https://laterbase.dev/mcp"
    }
  }
}

The first time the server starts, VS Code asks you to trust it and to let it sign in. Allow both, then sign in to Laterbase in the browser tab that opens and allow VS Code.

Check it works

MCP: List Servers shows laterbase as running. In Chat, Configure Tools lists its tools, and typing /laterbase shows the skills. The sign-in is listed under Connected apps on Connections.

Disconnect

Pick Uninstall for laterbase in MCP: List Servers, or delete its entry from mcp.json. To revoke its access from this side, press Disconnect next to it under Connected apps on Connections.

With an API key

If you'd rather not sign in, add the server with an API key.

1. Sign in, open Connections on the dashboard and create an API key. It's shown once, so copy it into the snippet straight away. One key per machine keeps things tidy.
2. In VS Code, run MCP: Open User Configuration from the Command Palette and add the server to servers.

// mcp.json
{
  "servers": {
    "laterbase": {
      "type": "http",
      "url": "https://laterbase.dev/mcp",
      "headers": { "Authorization": "Bearer lb_live_your_key" }
    }
  }
}

In more than one workspace? Add one server per workspace, each with its own key and a name like laterbase-acme, so agents can work in both at once. See Workspaces and connections.

MCP: List Servers shows laterbase as running.

Pick Uninstall for laterbase in MCP: List Servers, or delete its entry from mcp.json. To cut it off for good, revoke the key on Connections. Agents using it stop working on their next call.