systemprompt-mcp-notion and Notion-MCP

These two tools are competitors, with Ejb503/systemprompt-mcp-notion being the more widely recognized (and likely official) Model Context Protocol (MCP) server for Notion, while ghubnerr/Notion-MCP is an earlier, independent implementation aiming to achieve the same integration.

Notion-MCP
25
Experimental
Maintenance 0/25
Adoption 7/25
Maturity 18/25
Community 18/25
Maintenance 0/25
Adoption 3/25
Maturity 9/25
Community 13/25
Stars: 26
Forks: 13
Downloads:
Commits (30d): 0
Language: TypeScript
License:
Stars: 4
Forks: 2
Downloads:
Commits (30d): 0
Language: TypeScript
License: MIT
Stale 6m
Stale 6m No Package No Dependents

About systemprompt-mcp-notion

Ejb503/systemprompt-mcp-notion

This an Model Context Protocol (MCP) server that integrates Notion into your AI workflows. This server enables seamless access to Notion through MCP, allowing AI agents to interact with pages, databases, and comments.

Leverages MCP Sampling to enable AI agents to create and update Notion content dynamically, while integrating with the SystemPrompt platform for API key management. Built with TypeScript and Jest test coverage, the server communicates via stdio transport with MCP-compatible clients like Claude Desktop and the SystemPrompt multimodal client. Requires separate Notion integration tokens and SystemPrompt API credentials for workspace access and content operations.

About Notion-MCP

ghubnerr/Notion-MCP

A Model Context Protocol (MCP) server for integrating with Notion workspaces (made before the official one 😅)

Scores updated daily from GitHub, PyPI, and npm data. How scores work