Notion MCP Server

Created By
awkoya year ago
**Notion MCP Server** is a Model Context Protocol (MCP) server implementation that enables AI assistants to interact with Notion's API. This production-ready server provides a complete set of tools.
Overview

What is Notion MCP Server?

Notion MCP Server is a Model Context Protocol (MCP) server implementation that allows AI assistants to interact with Notion's API, providing a comprehensive set of tools for managing Notion content.

How to use Notion MCP Server?

To use Notion MCP Server, obtain a Notion API key, set up the integration with your Notion pages, and then use your AI assistant to perform actions like creating or updating pages.

Key features of Notion MCP Server?

  • Notion Integration: Seamlessly interact with Notion databases, pages, and blocks.
  • Universal MCP Compatibility: Works with various MCP clients including Cursor and Claude Desktop.
  • Data Retrieval: Fetch information from Notion pages and databases.
  • Content Creation: Create and update Notion content through natural language.
  • Batch Operations: Perform multiple operations in a single request.

Use cases of Notion MCP Server?

  1. Automating task management by creating pages for daily tasks.
  2. Updating meeting notes in Notion through voice commands.
  3. Archiving and restoring pages as needed.

FAQ from Notion MCP Server?

  • What is the Model Context Protocol?

MCP is a protocol that allows AI systems to interact with various APIs in a standardized way.

  • Is there a cost to use Notion MCP Server?

No, it is free to use as it is an open-source project.

  • What programming language is used?

The server is built using TypeScript.

Server Config

{
  "mcpServers": {
    "notion-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "notion-mcp-server"
      ],
      "env": {
        "NOTION_TOKEN": "YOUR_KEY",
        "NOTION_PAGE_ID": "YOUR_PAGE_ID"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
awkoy
Star
87
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago