Notion API MCP Server
Create and manage Notion pages, databases, and blocks through your AI agent.
Quick Start Summary
The Notion API MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Notion API API through natural language. It exposes 3 API endpoints as callable tools, such as Create a page, Query a database, Get block children. Authentication requires OAuth2 credentials, and setup takes approximately 2 minutes. The server uses STDIO transport and can be installed by running npx -y @modelcontextprotocol/server-notion. This integration is sourced from the official Notion API OpenAPI specification (v2022-06-28) and has a quality score of 78/99 (good documentation coverage).
Server Details
- Category
- Productivity
- Authentication
- OAuth2
- Endpoints
- 3 operations
- Transport
- STDIO
- Spec Version
- v2022-06-28
- Install Command
npx -y @modelcontextprotocol/server-notion
Environment Variables
NOTION_TOKENExample: ntn_...
Top Endpoints
/v1/pagesCreate a page
/v1/databases/{database_id}/queryQuery a database
/v1/blocks/{block_id}/childrenGet block children
Build with Notion API
Get everything you need in one bundle: MCP config, cursor rules, and framework integration for Notion API.
View Notion + Python Productivity Stack→Read the Guide
Step-by-step walkthrough for setting up and using the Notion API MCP server.
Notion APIMCP Setup Guide →One-Click Install
Copy the snippet for your MCP client and paste it in — zero editing required.
Claude Desktop
Add to claude_desktop_config.json
{
"mcpServers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-notion"
],
"env": {
"NOTION_TOKEN": "ntn_..."
}
}
}
}Cursor
Settings → MCP Servers → Add
{
"mcpServers": {
"notion": {
"url": "https://mcpbridge.org/config/notion.json"
}
}
}Saves as .cursor/mcp.json in the download. Move it to your project root.
VS Code
Use with MCP extension
{
"mcpServers": {
"notion": {
"url": "https://mcpbridge.org/config/notion.json"
}
}
}Endpoints Explorer
Search and browse the 3 operations supported by this server.
Multi-Language Code Examples
Executable code snippets for calling Notion API endpoints in curl, TypeScript, or Python.
curl -X POST "https://raw.githubusercontent.com/notionhq/notion-sdk-py/main/openapi.yml/v1/pages" \ -H "Content-Type: application/json" \ -H "Authorization: YOUR_API_KEY"
Manual Configuration
Directly add this block to your JSON config file, or use the hosted config registry URL.
{
"mcpServers": {
"notion": {
"command": "npx",
"args": ["-y","@modelcontextprotocol/server-notion"],
"env": {
"NOTION_TOKEN": "ntn_..."
}
}
}
}Authentication Details
This API requires OAuth2 credentials.
Variables to configure:
NOTION_TOKEN
Documentation Links
Error Handling & HTTP Status Code Matrix
Common status codes, error causes, and resolution steps when invoking Notion API endpoints.
400 Bad RequestCause: Malformed payload parameters or missing required fields.
Resolution: Verify request schema in Endpoints tab before calling tool.
401 UnauthorizedCause: Missing or invalid API key credentials.
Resolution: Set environment variable in MCP client config under env object.
403 ForbiddenCause: Insufficient scope permissions for requested resource.
Resolution: Verify key permissions in developer dashboard.
404 Not FoundCause: Resource URL path or requested entity ID does not exist.
Resolution: Check path variables and parameters.
429 Rate Limit ExceededCause: API rate limit quota exceeded.
Resolution: Implement exponential backoff retry in tool call.
500 Internal ErrorCause: Upstream server runtime fault.
Resolution: Inspect STDIO stderr output for log trace.
Quality Score
Checked against our protocol-compliance rules.
Specification Version: v2022-06-28
Page compiled on: June 13, 2026
This listing has been claimed and verified by the API owner.
Similar APIs
Other APIs in the Productivity category.
Linear API
Manage issues, projects, and workflows in Linear through your AI agent.
API KeyPlatform API
The Platform API is a comprehensive RESTful interface provided by Ably, a leading provider of real-time messaging and presence infrastructure, designed to give developers granular, programmatic control over their Ably applications and resources. Its core capabilities extend beyond simple pub/sub messaging, enabling the management and inspection of channels, the retrieval and publishing of messages, the manipulation of presence state for users across those channels, and the configuration of push notification subscriptions. Typical use cases span enterprise and consumer applications where real-time functionality is critical, such as live activity feeds for e-commerce platforms, collaborative tools requiring synchronized state, multi-user gaming, real-time chat, and IoT device status monitoring. This API serves as the foundational control plane for any application built on the Ably ecosystem, allowing for dynamic, server-side orchestration of real-time behaviors.
Control API v1
The Control API v1, provided by Ably, is a comprehensive programmatic interface designed for the administrative management and automation of Ably’s real-time messaging infrastructure. It serves as the central nervous system for controlling core resources within an Ably account, enabling developers and platform engineers to dynamically provision and configure applications, manage authentication credentials (keys), organize message flow with namespaces, and establish operational rules. Its primary function is to transition infrastructure management from manual, dashboard-driven tasks to scalable, code-first operations. This makes it indispensable for enterprise use cases such as automated environment provisioning for development and testing, multi-tenant SaaS platforms requiring isolated customer channels, and large-scale IoT deployments where device groups (represented by namespaces) or security credentials (keys) must be managed programmatically in response to dynamic demand. The API currently operates in a Beta state, indicating it is feature-rich but subject to refinement based on developer feedback.
Adyen Test Cards API
The Adyen Test Cards API, provided by the global payment platform Adyen, is a specialized utility designed to streamline the payment integration development and testing lifecycle. Its core capability is the programmatic generation of custom test card numbers, a critical requirement for developers and QA engineers building and validating payment flows in sandbox or test environments. By exposing a dedicated endpoint, `POST /createTestCardRanges`, the API eliminates the manual process of sourcing static test card numbers from documentation or community lists. This is particularly valuable for enterprise-scale applications where testing must cover a complex matrix of scenarios, including various card schemes (Visa, Mastercard, etc.), card types (credit, debit, prepaid), issuer countries, and specific transaction outcomes like approvals, declines, and 3D Secure challenges. Typical use cases span from automated continuous integration (CI) pipelines that require unique test data for each run, to teams developing payment interfaces that must simulate a wide array of real-world customer payment methods.
Related MCP Server Integrations
Linear API MCP Setup
Manage issues, projects, and workflows in Linear through your AI agent.
Platform API MCP Setup
The Platform API is a comprehensive RESTful interface provided by Ably, a leading provider of real-time messaging and presence infrastructure, designed to give developers granular, programmatic control over their Ably applications and resources. Its core capabilities extend beyond simple pub/sub messaging, enabling the management and inspection of channels, the retrieval and publishing of messages, the manipulation of presence state for users across those channels, and the configuration of push notification subscriptions. Typical use cases span enterprise and consumer applications where real-time functionality is critical, such as live activity feeds for e-commerce platforms, collaborative tools requiring synchronized state, multi-user gaming, real-time chat, and IoT device status monitoring. This API serves as the foundational control plane for any application built on the Ably ecosystem, allowing for dynamic, server-side orchestration of real-time behaviors.
Control API v1 MCP Setup
The Control API v1, provided by Ably, is a comprehensive programmatic interface designed for the administrative management and automation of Ably’s real-time messaging infrastructure. It serves as the central nervous system for controlling core resources within an Ably account, enabling developers and platform engineers to dynamically provision and configure applications, manage authentication credentials (keys), organize message flow with namespaces, and establish operational rules. Its primary function is to transition infrastructure management from manual, dashboard-driven tasks to scalable, code-first operations. This makes it indispensable for enterprise use cases such as automated environment provisioning for development and testing, multi-tenant SaaS platforms requiring isolated customer channels, and large-scale IoT deployments where device groups (represented by namespaces) or security credentials (keys) must be managed programmatically in response to dynamic demand. The API currently operates in a Beta state, indicating it is feature-rich but subject to refinement based on developer feedback.
Adyen Test Cards API MCP Setup
The Adyen Test Cards API, provided by the global payment platform Adyen, is a specialized utility designed to streamline the payment integration development and testing lifecycle. Its core capability is the programmatic generation of custom test card numbers, a critical requirement for developers and QA engineers building and validating payment flows in sandbox or test environments. By exposing a dedicated endpoint, `POST /createTestCardRanges`, the API eliminates the manual process of sourcing static test card numbers from documentation or community lists. This is particularly valuable for enterprise-scale applications where testing must cover a complex matrix of scenarios, including various card schemes (Visa, Mastercard, etc.), card types (credit, debit, prepaid), issuer countries, and specific transaction outcomes like approvals, declines, and 3D Secure challenges. Typical use cases span from automated continuous integration (CI) pipelines that require unique test data for each run, to teams developing payment interfaces that must simulate a wide array of real-world customer payment methods.
Amazon Lex Runtime V2 MCP Setup
Amazon Lex Runtime V2 is a sophisticated conversational AI service provided by Amazon Web Services that enables developers to manage and interact with chatbot sessions in real time. This API serves as the runtime interface for Amazon Lex bots, allowing applications to communicate with bots that have already been built and published. The service is designed to handle natural language understanding and dialogue management at scale, supporting multiple languages and locales within a single bot configuration. Typical enterprise use cases include deploying intelligent virtual agents for customer service portals, automating FAQ responses in e-commerce platforms, integrating voice and text-based conversational interfaces into enterprise applications, and powering interactive voice response systems for contact centers. Consumer-facing applications often leverage Lex V2 for personal assistant functionality, appointment scheduling bots, and interactive troubleshooting guides. The Runtime V2 API is distinct from the Build-time API, as it focuses exclusively on session-based interactions rather than bot creation or training, making it the critical endpoint for any production deployment that requires real-time user engagement.