Skip to main content
Book a demo

Connect Notion to VS Code

Give VS Code governed access to Notion’s 48 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add Notion to VS Code in four steps

Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.

  1. 1

    Approve Notion in Runlayer

    Add Notion from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Notion’s 48 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 3

    Sign in to Notion

    Sign in the way Notion requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Notion from VS Code

    Notion’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

48 Notion tools in VS Code

Runlayer policy decides which of these VS Code users can call. 5 read data only and 1 can change or delete data.

  • AI search

    Notion ai search.

  • Check MCP next steps

    Finish all Notion tool calls needed for the current request, then call at most once with no arguments.

  • Convert page to skill

    Mark an existing Notion page as a skill without changing its content.

  • Create attachment

    Create an attachment and upload it to Notion.

  • Create comment

    Add a comment to a page or specific content.

  • Create database

    Creates a new Notion database using SQL DDL syntax, or a canonical typed database for tasks, projects, or skills.

  • Create file upload

    Create a short-lived URL for uploading one local file directly to Notion.

  • Create folder

    Creates an empty Notion Folder.

See all 48 Notion tools

Control

What Runlayer can see and stop in VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Notion call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination