Notion MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Notion MCP Server?

Notion MCP Server is a Model Context Protocol (MCP) server that allows AI models to interact with Notion workspaces through the official Notion SDK.

how to use Notion MCP Server?

To use the Notion MCP Server, set up your Notion integration by creating a new integration on Notion, copying the API key, and sharing your Notion pages with the integration. Then, you can add the MCP server to your AI assistant using command line or JSON configuration formats.

key features of Notion MCP Server?

  • Full support for the Notion API through the official SDK.
  • MCP compliant for seamless integration with AI models.
  • Tools for searching, querying databases, managing pages, and more.
  • Robust error handling and detailed troubleshooting guidance.

use cases of Notion MCP Server?

  1. Integrating AI assistants with Notion for enhanced productivity.
  2. Automating content management tasks within Notion workspaces.
  3. Enabling AI-driven insights and data retrieval from Notion databases.

FAQ from Notion MCP Server?

  • How do I set up the Notion integration?

Go to Notion's integration page, create a new integration, and share your pages with it.

  • What tools does the server provide?

The server provides tools for searching, managing databases, pages, blocks, users, comments, and link previews.

  • What should I do if I encounter errors?

Refer to the troubleshooting section in the documentation for common issues and solutions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
Apache-2.0 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