Setup guides

Connect Nickbox to VS Code

Add Nickbox as an HTTP MCP server in VS Code, from the command palette or .vscode/mcp.json.

Updated · 1 min read

VS Code adds Nickbox as an HTTP MCP server, either from the command palette or with a small JSON file.

Before you start

  • A recent VS Code with MCP support and an agent chat available.
  • A Nickbox account with at least one inbox connected.
  • Your MCP URL: https://nickbox.io/mcp here; the real one is in the dashboard under Connect.

Option A: command palette

  1. Open the command palette and run MCP: Add Server.

  2. Choose HTTP.

  3. Paste the URL:

    https://nickbox.io/mcp
    
  4. Name it nickbox and choose where to save it: your user profile, or the current workspace.

  5. When VS Code asks, allow it to open the browser, sign in with Google and approve read-only access.

Option B: edit the file

Create .vscode/mcp.json in your workspace:

{
  "servers": {
    "nickbox": {
      "type": "http",
      "url": "https://nickbox.io/mcp"
    }
  }
}

Note that VS Code uses servers, not mcpServers. Save the file, then start the server from the inline Start action above the entry. VS Code opens the browser for sign-in.

Check it works

Open chat in agent mode, open the tools picker and confirm the Nickbox tools are enabled. Then ask:

list my inboxes

You should see your nicknames. VS Code asks before running a tool the first time.

Troubleshooting

  • MCP: Add Server is missing. Update VS Code, or check that your organization has not disabled MCP.
  • The server will not start. Run MCP: List Servers, select nickbox and open its output to see the error.
  • You used mcpServers and nothing happened. Change it to servers in .vscode/mcp.json.
  • Sign-in expired. Run MCP: List Servers, choose nickbox and restart or sign in again.
  • Google blocks sign-in on Workspace. See the Workspace admin guide.

Want every inbox in one assistant?

Try Nickbox for seven days. The beta is limited, so places are few.

Start your 7-day trial