Skip to content

Will this MCP server be updated to support the newest API version? #139

@nofrontsec

Description

@nofrontsec

As noted here, the last API update changed how Database interactions work.
Will the Notion OSS MCP tools and their schemas be updated to reflect this change, or are users expected to fend for themselves?
As far as I can tell, none of the tools exposed by the official remote MCP server currently reflect this change, this leads to issues when working with DBs with multiple data sources. Something else that's strange; the available tools listed in the docs don't even share their names with the ones I see available in my MCP clients (5ire, Cherry):

Image

Example: the tool notion-fetch, as described in the docs and Claude Desktop, doesn't exist in the tools supplied by notion-mcp-server on NPM. This is the tool used by Claude to fetch pages and DBs (along with an array of data-source-id s which claude then uses to work with data stored in the DBs).

Overall they seem like completely different tools when I compare their schemas and what they do. When I checked the Notion tools available to Claude (when used with Claude Desktop) via Settings -> Connections -> Notion -> configure, I noticed that they are functionally identical to the tools I found in the docs.

Currently, the only way for me to agentically interact with my content in Notion is via Claude Desktop with its official (and, I assume, closed-source) Notion connector/integration. This is unsustainable, as using the Desktop App instead of the API to interact with Claude/Ghidra/Notion usually leads to me hitting the Pro plan session limit in less than 10 prompts

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions