Home / MCP registry index / Topics / Notion
Notion MCP servers, with their tools checked
Every server in the official MCP registry that mentions Notion, with a public endpoint, read the way an MCP client reads it and checked for tool poisoning. The list updates as the registry does, and each server is read again every week.
8 listed. We have read the tools of 1 so far; the others want credentials first, could not be reached, or are still waiting for their first read.
These servers act inside an account you own, usually with a token you give them. Prefer the narrowest access the tools need, and check which tools can send, post or delete.
| Context Link ai.context-link/context-link | 4 tools, nothing matched 2026-10-21 |
| Notion MCP by InsightfulPipe com.insightfulpipe/notion | not read yet |
| com.notion/mcp com.notion/mcp | not read yet |
| Notion_connect io.github.pipeworx-io/notion_connect | not read yet |
| io.github.Ranork/remnus io.github.Ranork/remnus | not read yet |
| Notion URL Shape io.github.sadri-dridi/notion-url-shape | not read yet |
| MagicInterview io.github.samihalawa/magicinterview | not read yet |
| Commentify one.commentify/commentify | not read yet |
Choosing one
Open a server's page to see the tools it advertises, whether it sets instructions for the model, and our latest read. Here, 1 of the servers shown matched none of our tool-poisoning rules on their last read. A clean read means our rules found nothing, not that a server is harmless; still check what access it asks for. To check one that is not listed, paste its URL into the free MCP server check.
Related: GitHub · GitLab · Slack · Discord · Email · Calendar · Google Workspace · Jira and Confluence · all topics