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 server designed for integrating Notion with Claude and other LLMs, enabling seamless interaction with your Notion workspace.

how to use Notion MCP Server?

To use the Notion MCP Server, clone the repository, install dependencies, configure your Notion API key, build the server, and run it. Connect it with Claude for Desktop to start using it.

key features of Notion MCP Server?

  • Search across your entire Notion workspace
  • Retrieve content from specific Notion pages
  • Create and update pages in Notion
  • Create and query databases with custom properties
  • Update database entries and add new rows to existing databases

use cases of Notion MCP Server?

  1. Searching for meeting notes in Notion
  2. Retrieving project planning content from Notion
  3. Creating new pages for task management
  4. Updating existing pages with new information
  5. Querying databases for specific entries based on filters

FAQ from Notion MCP Server?

  • Can I use Notion MCP Server with any LLM?

Yes! It is designed to work with Claude and other LLMs that support Model Context Protocol.

  • Is there a cost to use Notion MCP Server?

No! The Notion MCP Server is free to use.

  • What do I need to set up the server?

You need to clone the repository, install dependencies, and configure your Notion API key.

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

a day ago