How to integrate Notion MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Notion logo
Claude Agent SDK logo
divider

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.

Supported Tools & Triggers

Tools
Triggers
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 blocksAppend 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 PageArchives (moves to trash) or unarchives (restores from trash) a specified Notion page.
Create commentAdds 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 DatabaseCreates a new Notion database as a subpage under a specified parent page with a defined properties schema.
Create Notion file uploadTool to create a Notion FileUpload object and retrieve an upload URL.
Create Notion pageCreates a new page in a Notion workspace under a specified parent page or database.
Delete a blockArchives 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 pageDuplicates a Notion page, including all its content, properties, and nested blocks, under a specified parent page or workspace.
Fetch All Notion Block ContentsTool to fetch all child blocks for a given Notion block.
Fetch Notion Block ChildrenRetrieves 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 metadataFetches metadata for a Notion block (including pages, which are special blocks) using its UUID.
Fetch commentsFetches unresolved comments for a specified Notion block or page ID.
Fetch Notion DataFetches 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 DatabaseFetches a Notion database's structural metadata (properties, title, etc.
Fetch database rowRetrieves a Notion database row's properties and metadata; use fetch_block_contents for page content blocks.
Get about userRetrieves detailed information about a specific Notion user, such as their name, avatar, and email, based on their unique user ID.
Get page markdownRetrieve a Notion page's full content rendered as Notion-flavored Markdown in a single API call.
Get page propertyCall 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 databaseCreates a new page (row) in a specified Notion database.
Insert Row From Natural LanguageCreates a new row (page) in a Notion database from a natural language description.
List data source templatesTool to list all templates for a Notion data source.
List Notion file uploadsTool to retrieve file uploads for the current bot integration, sorted by most recent first.
List usersRetrieves 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 PageTool to move a Notion page to a new parent (page or database).
Query databaseQueries a Notion database to retrieve pages (rows).
Query database with filterTool to query a Notion database with server-side filtering, sorting, and pagination.
Query data sourceTool 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 CommentTool to retrieve a specific comment by its ID.
Retrieve Database PropertyTool to retrieve a specific property object of a Notion database.
Retrieve Notion file uploadTool to retrieve details of a Notion File Upload object by its identifier.
Retrieve pageRetrieve a Notion page's properties/metadata (not block content) by page_id.
Search Notion pages and databasesSearches Notion pages and databases by title.
Send file uploadTool to transmit file contents to Notion for a file upload object.
Update blockUpdates existing Notion block's text content.
Update PageUpdate 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 schemaUpdates an existing Notion database's schema including title, description, and/or properties (columns).
Upsert database rowsTool to upsert rows in a Notion database by querying for existing rows and creating or updating them.

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

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

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.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

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

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

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

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Notion
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["notion"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
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

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Notion tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="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
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

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

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Notion
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["notion"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Notion tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

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.

How to build Notion MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Notion MCP?

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.

Can I use Tool Router MCP with Claude Agent SDK?

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.

Can I manage the permissions and scopes for Notion while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.