Skip to main content
Book a demo

Connect Notion to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Notion to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI 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 Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Notion’s 48 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI 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 Cline CLI

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

Tools

48 Notion tools in Cline CLI

Runlayer policy decides which of these Cline CLI 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 Cline CLI

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI 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 Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination