Notion MCP Server
@nanahiryu
Notion MCP Server について
概要はまだありません
基本情報
設定
ツール
ツールは検出されませんでした
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
概要
What is Notion MCP Server?
A server that integrates with Notion's API using the Model Context Protocol (MCP), designed to function as an MCP server for Cursor.
How to use Notion MCP Server?
Clone the repository, run npm i and npm run build, then configure it in Cursor by adding a new MCP server with the command that sets NOTION_API_TOKEN environment variable and points to the built index.js.
Key features of Notion MCP Server
- Block operations (add, retrieve, get children, delete)
- Page operations (retrieve, update properties)
- User information retrieval
- Database operations (create, query, retrieve, update, create items)
- Comment operations (create, retrieve)
Use cases of Notion MCP Server
—
FAQ from Notion MCP Server
—
(Note: Since the README does not contain any FAQ content, the skeleton requires "—" for each FAQ question and answer. The instruction says to include 3–5 FAQs only if the README has answers; if none, we still output the skeleton with "—" for each. However, the skeleton shows "[Question 1]?" and "[1–2 sentence answer.]" — we need to output exactly that with "—". But the skeleton also says "Only include FAQs the README has answers for." That implies we can omit the entire FAQ section if no answers exist. To be safe, we will include the FAQ subheadings but with "—" for both question and answer, as per the instruction to "follow the SKELETON below verbatim". Actually the skeleton shows:
[Question 1]?
[1–2 sentence answer.]
But it says "Only include FAQs the README has answers for." So if no FAQs, we should not include the FAQ section at all. Or we can output the H2 and then "—". The instruction is ambiguous. I think the safest is to omit the entire FAQ section. The skeleton states: "If a section can't be answered from the README, output a single em dash — as its body." That applies to the H2 body, not the H2 itself. Since FAQ is an H2 section, if no FAQs are present, we should output "—" for that section? But then the skeleton has subheadings. Given the strict rule "Follow the SKELETON below verbatim", I will include the FAQ H2 and put "—" as its body, meaning no subheadings. However the skeleton shows indented ### questions. I think the best interpretation: if there are no FAQs, just put "—" under "FAQ from Notion MCP Server" as the entire body. I'll do that.
But to be precise, I'll output:
FAQ from Notion MCP Server
—
That matches the rule. I'll proceed.## What is Notion MCP Server?
A server that integrates with Notion's API using the Model Context Protocol (MCP), designed to function as an MCP server for Cursor.
How to use Notion MCP Server?
Clone the repository, run npm i and npm run build, then configure it in Cursor by adding a new MCP server with the command that sets NOTION_API_TOKEN environment variable and points to the built index.js.
Key features of Notion MCP Server
- Block operations (add, retrieve, get children, delete)
- Page operations (retrieve, update properties)
- User information retrieval
- Database operations (create, query, retrieve, update, create items)
- Comment operations (create, retrieve)
Use cases of Notion MCP Server
—
FAQ from Notion MCP Server
—
「メモリとナレッジ」の他のコンテンツ
MCP Apple Notes
RafalWilinskiTalk with your notes in Claude. RAG over your Apple Notes using Model Context Protocol.
Ultimate Google Docs & Drive MCP Server
a-bonusThe Ultimate Google Docs, Sheets, Drive, Gmail, & Google Calendar MCP Server. This MCP (primarily for use in Claude Desktop) gains full access to your google suite and lets claude do its thing.
Semantic Scholar MCP Server
YUZongminA FastMCP server implementation for the Semantic Scholar API, providing comprehensive access to academic paper data, author information, and citation networks.
Notion MCP Server
suekouA Model Context Protocol server for connecting Notion to MCP-compatible clients
Context7 MCP - Up-to-date Docs For Any Cursor Prompt
upstashContext7 Platform -- Up-to-date code documentation for LLMs and AI code editors
コメント