Evan
c25a321e88
* fix: pin npm package versions in MCP integration templates Prevent supply chain attacks by pinning exact versions instead of using unpinned `npx -y @package` which pulls latest on every run. 23 of 25 integrations pinned. sqlite-mcp and aws skipped (packages not found on npm registry). * fix: use stable azure/mcp version instead of beta
29 lines
976 B
TOML
29 lines
976 B
TOML
id = "notion"
|
|
name = "Notion"
|
|
description = "Access and manage Notion pages, databases, and blocks through the MCP server"
|
|
category = "productivity"
|
|
icon = "📝"
|
|
tags = ["notes", "wiki", "knowledge-base", "documentation", "databases"]
|
|
|
|
[transport]
|
|
type = "stdio"
|
|
command = "npx"
|
|
args = ["-y", "@notionhq/notion-mcp-server@2.2.1"]
|
|
|
|
[[required_env]]
|
|
name = "NOTION_API_KEY"
|
|
label = "Notion Integration Token"
|
|
help = "An internal integration token created in your Notion workspace settings"
|
|
is_secret = true
|
|
get_url = "https://www.notion.so/my-integrations"
|
|
|
|
[health_check]
|
|
interval_secs = 60
|
|
unhealthy_threshold = 3
|
|
|
|
setup_instructions = """
|
|
1. Go to https://www.notion.so/my-integrations and click 'New integration'.
|
|
2. Give it a name, select your workspace, and grant the required capabilities (Read/Update/Insert content).
|
|
3. Copy the Internal Integration Token and paste it into the NOTION_API_KEY field above. Then share relevant pages with the integration in Notion.
|
|
"""
|