notion-export-mcp-server

Created By
syucreama year ago
A MCP server that accesses to Notion unofficial API to export pages.
Overview

What is Notion Export MCP Server?

Notion Export MCP Server is a server that provides access to Notion's unofficial API, allowing users to export pages in a standardized format using the Model Context Protocol (MCP).

How to use Notion Export MCP Server?

To use the server, install it via npm, configure your Notion tokens, and start the server using the provided commands.

Key features of Notion Export MCP Server?

  • Access to Notion's unofficial API for page exports.
  • MCP-compatible interface for AI assistants.
  • Simple installation and configuration process.

Use cases of Notion Export MCP Server?

  1. Exporting Notion pages for use in AI applications.
  2. Integrating Notion data with other tools via MCP.
  3. Facilitating data access for developers working with Notion.

FAQ from Notion Export MCP Server?

  • Is this server official?

No, it accesses Notion's unofficial API.

  • How do I install the server?

You can install it using npm with the command npm install notion-export-mcp-server.

  • What tokens do I need to configure?

You need to configure NOTION_TOKEN_V2 and NOTION_FILE_TOKEN.

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

a day ago