How to integrate Notion MCP with Claude Agent SDK

This guide walks you through connecting Notion to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Notion agent that can add meeting notes to project wiki page, create a new task database for q3, archive completed sprint summary pages through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Notion account through Composio's Notion MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Notion logoNotion
Oauth2Api Key

Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.

45 Tools13 Triggers

Introduction

This guide walks you through connecting Notion to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Notion agent that can add meeting notes to project wiki page, create a new task database for q3, archive completed sprint summary pages through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Notion account through Composio's Notion MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Notion with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Notion
  • Configure an AI agent that can use Notion as a tool
  • Run a live chat session where you can ask the agent to perform Notion operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Notion MCP server, and what's possible with it?

The Notion MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Notion account. It provides structured and secure access to your notes, docs, wikis, and tasks, so your agent can perform actions like creating pages, managing databases, adding content, commenting, and organizing your Notion workspace for you.

  • Bulk content creation and formatting: Let your agent efficiently add and format multiple blocks of text, lists, or markdown content to Notion pages in one go.
  • Automated page and database management: Have your agent create new pages, duplicate existing ones, or set up entire databases with custom properties—no manual setup required.
  • Smart commenting and collaboration: Enable your agent to add comments to pages or discussion threads, making real-time collaboration smoother.
  • Workspace organization and cleanup: Ask your agent to archive, delete, or restore pages and blocks, keeping your workspace tidy and up to date.
  • Deep block and structure retrieval: Direct your agent to fetch metadata, list child blocks, or dig into nested content for analysis, reporting, or workflow automation.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Notion account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Notion functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Notion
  const session = await composio.create(USER_ID, {
    toolkits: ['notion'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Notion
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Notion tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Notion
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Notion and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['notion']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Notion tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Notion through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS & TRIGGERS

Supported Tools and Triggers

Every Notion action and event your agent gets out of the box.

Add multiple content blocks (bulk, user-friendly)

Bulk-add content blocks to Notion.

Append code blocks (code, quote, equation)

Append code and technical blocks (code, quote, equation) to a Notion page.

Append layout blocks (divider, TOC, columns)

Append layout blocks (divider, TOC, breadcrumb, columns) to a Notion page.

Append media blocks (image, video, audio, files)

Append media blocks (image, video, audio, file, pdf, embed, bookmark) to a Notion page.

Append table blocks

Append table blocks to a Notion page.

Append task blocks (to-do, toggle, callout)

Append task blocks (to-do, toggle, callout) to a Notion page or block.

Append text blocks (paragraphs, headings, lists)

Append text blocks (paragraphs, headings, lists) to a Notion page.

Archive Notion Page

Archives (moves to trash) or unarchives (restores from trash) a specified Notion page.

Create comment

Adds a comment to a Notion page (via `parent_page_id`) OR to an existing discussion thread (via `discussion_id`); cannot create new discussion threads on specific blocks (inline comments).

Create Notion Database

Creates a new Notion database as a subpage under a specified parent page with a defined properties schema.

Create Notion file upload

Tool to create a Notion FileUpload object and retrieve an upload URL.

Create Notion page

Creates a new page in a Notion workspace under a specified parent page or database.

Delete a block

Archives a Notion block, page, or database using its ID, which sets its 'archived' property to true (like moving to "Trash" in the UI) and allows it to be restored later.

Duplicate page

Duplicates a Notion page, including all its content, properties, and nested blocks, under a specified parent page or workspace.

Fetch All Notion Block Contents

Tool to fetch all child blocks for a given Notion block.

Fetch Notion Block Children

Retrieves a paginated list of direct, first-level child block objects along with contents for a given parent Notion block or page ID; use block IDs from the response for subsequent calls to access deeply nested content.

Fetch Notion block metadata

Fetches metadata for a Notion block (including pages, which are special blocks) using its UUID.

Fetch comments

Fetches unresolved comments for a specified Notion block or page ID.

Fetch Notion Data

Fetches Notion items (pages and/or databases) from the Notion workspace, use this to get minimal data about the items in the workspace with a query or list all items in the workspace with minimal data

Fetch Database

Fetches a Notion database's structural metadata (properties, title, etc.

Fetch database row

Retrieves a Notion database row's properties and metadata; use fetch_block_contents for page content blocks.

Get about user

Retrieves detailed information about a specific Notion user, such as their name, avatar, and email, based on their unique user ID.

Get page markdown

Retrieve a Notion page's full content rendered as Notion-flavored Markdown in a single API call.

Get page property

Call this to get a specific property from a Notion page when you have a valid `page_id` and `property_id`; handles pagination for properties returning multiple items.

Insert row database

Creates a new page (row) in a specified Notion database.

Insert Row From Natural Language

Creates a new row (page) in a Notion database from a natural language description.

List data source templates

Tool to list all templates for a Notion data source.

List Notion file uploads

Tool to retrieve file uploads for the current bot integration, sorted by most recent first.

List users

Retrieves a paginated list of users (excluding guests) from the Notion workspace; the number of users returned per page may be less than the requested `page_size`.

Move Page

Tool to move a Notion page to a new parent (page or database).

Query database

Queries a Notion database to retrieve pages (rows).

Query database with filter

Tool to query a Notion database with server-side filtering, sorting, and pagination.

Query data source

Tool to query a Notion data source.

Replace page content (with backup)

Safely replaces a page's child blocks by optionally backing up current content, deleting existing children, then appending new children in batches.

Retrieve Comment

Tool to retrieve a specific comment by its ID.

Retrieve Database Property

Tool to retrieve a specific property object of a Notion database.

Retrieve Notion file upload

Tool to retrieve details of a Notion File Upload object by its identifier.

Retrieve page

Retrieve a Notion page's properties/metadata (not block content) by page_id.

Search Notion pages and databases

Searches Notion pages and databases by title.

Send file upload

Tool to transmit file contents to Notion for a file upload object.

Update block

Updates existing Notion block's text content.

Update Page

Update page properties, icon, cover, or archive status.

Update Database Row (Page)

Updates a specific row/page within a Notion database by its page UUID (row_id).

Update database schema

Updates an existing Notion database's schema including title, description, and/or properties (columns).

Upsert database rows

Tool to upsert rows in a Notion database by querying for existing rows and creating or updating them.

FAQ

Frequently asked questions

With a standalone Notion MCP server, the agents and LLMs can only access a fixed set of Notion tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Notion and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Notion tools.

Yes, absolutely. You can configure which Notion scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Notion data and credentials are handled as safely as possible.

Start with Notion.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Notion tool your agent needs.Free to start.

Start building