Notion MCP Server

Created By
KingGuizzarda year ago
A simple MCP server implementation for Notion integration
Overview

What is Notion MCP Server?

Notion MCP Server is a simple Model-Controller-Persistence (MCP) server implementation designed for seamless integration with Notion. It provides a REST API that simplifies interactions with Notion databases and pages.

How to use Notion MCP Server?

To use Notion MCP Server, clone the repository, install the necessary dependencies, set up your Notion API key and database ID in a .env file, and start the server using npm start.

Key features of Notion MCP Server?

  • REST API for easy interaction with Notion databases and pages.
  • Supports querying databases, creating pages, and managing blocks.
  • Simple setup process with clear instructions.

Use cases of Notion MCP Server?

  1. Automating data entry into Notion databases.
  2. Building applications that require dynamic interaction with Notion content.
  3. Integrating Notion with other services through API calls.

FAQ from Notion MCP Server?

  • What are the prerequisites for using Notion MCP Server?

You need Node.js (v14 or higher) and a Notion API key.

  • How do I get a Notion API key?

You can obtain it by creating a new integration in Notion and copying the Internal Integration Token.

  • Can I use this server for multiple Notion databases?

Yes! You can connect to multiple databases by configuring the respective database IDs in your setup.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
KingGuizzard
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago