Skip to content

Connect Notion (MCP token) to VS Code

Notion's hosted MCP server, reached with a token instead of a browser sign-in, so agents can connect with nobody there to approve it. Needs a Business or Enterprise plan.

MCP serverOfficialChecked 2026-11-16

Before you start

  • VS Code installed (see its MCP documentation (opens in a new tab)).
  • Notion (MCP token) is available on macOS, Windows, Linux and the web.
  • Only workspace owners on Business and Enterprise plans can create a token, with New MCP token in Notion's Developer portal. Set it as NOTION_MCP_TOKEN in your environment. On other plans, use the Notion entry, which signs in through your browser.
  1. Step 1: Add Notion (MCP token) to VS Code

    Add it to the workspace

    Add this to .vscode/mcp.json. It holds no token, so you can commit it to share it with your team.

    .vscode/mcp.json
    {
      "inputs": [
        {
          "type": "promptString",
          "id": "notion-token-token",
          "description": "Token for notion-token",
          "password": true
        }
      ],
      "servers": {
        "notion-token": {
          "type": "http",
          "url": "https://mcp.notion.com/mcp",
          "headers": {
            "Authorization": "Bearer ${input:notion-token-token}"
          }
        }
      }
    }
    Good to know
    • VS Code asks for the token the first time the server starts and stores it for you, so the file holds no secret.
  2. Step 2: Check it's connected

    Run MCP: List Servers from the Command Palette, then open Copilot Chat in Agent mode and check the tools picker.

  3. Step 3: Try a first request

    Ask VS Code something that only works with Notion (MCP token) connected:

    Say to VS Code
    Find the Notion database that tracks our design tasks and list what's due this week.

If it doesn't work

  • VS Code asks you to trust a server the first time it starts. Accept it, or the tools stay hidden.
  • code --add-mcp writes to your user profile, so the server works in every workspace.
  • Use MCP: List Servers → Show Output to see startup errors.