I’m currently testing the other tickets, but I first want to thank you for the effort you put into all of them. This looks like a huge leap forward. I really appreciate it, and I’ll provide feedback separately in the individual tickets.
To give you a bit of context and feedback on this ticket:
I completely understand your point about not implementing all features of the MCP protocol. I came to the topic of resources because the Notion MCP regularly fails when trying to fetch the enhanced Markdown documentation. I inspected the Notion MCP and noticed that this documentation is a resource, but Bolt AI, or the LLM, tries to fetch it as a page instead. That results in an HTTP 400 error because Bolt AI doesn’t support resources.
That’s the main issue here. It makes the Notion integration quite buggy because the model doesn’t know about the Markdown features of Notion pages. As a result, it tries to create pages using the wrong syntax, which then fails.
I found a workaround by providing the content of that resource as a page in my Notion workspace and referencing it in the system prompt. That works, but it’s still just a workaround.
Just so you know how I came to this topic: I noticed that neither ChatGPT nor Claude has this issue. If you’re saying they don’t support resources either, then I think they must have found another workaround in their custom Notion integration.
Daniel Nguyen
Team•
Apr 28
I see. I’m not familiar with Notion, never liked them. Can you help me understand the issue better. For example, what I need to do in my brand new Notion account to replicate the issue you’re having. Maybe the bug was something else.
Claude does support many features of the MCP protocol since they invented it.
ChatGPT doesn’t. But they don’t need to because OpenAI has this private “connection” setup with their partners. I’m pretty sure they have private API etc to access Notion in this case.
I’ll try my best when I could replicate the issue. Supporting MCP resources might be the cleanest way to solve it actually.
Maximilian Christl
•
Apr 28
Hi @Daniel Nguyen, i’m using
npx @modelcontextprotocol/inspector
to inspect the notion MCP. In the Create Page instructions you find this excerpt:
IMPORTANT: For the complete Markdown specification, always first fetch the MCP resource at notion://docs/enhanced-markdown-spec. Do NOT guess or hallucinate Markdown syntax. This spec is also applicable to other tools like update-page and fetch.
So if you tell it to create a page it tries to fetch this via the page fetch, which won’t work.
Telling it to create a new Notion Page with sample content should be enough.
Atleast with OpenAI Models, 5.4 or 5.5 i’m able to reproduce this behavior consistently.
Log in to comment and vote
Comments3
Maximilian Christl
Apr 28
Hi @Daniel Nguyen ,
I’m currently testing the other tickets, but I first want to thank you for the effort you put into all of them. This looks like a huge leap forward. I really appreciate it, and I’ll provide feedback separately in the individual tickets.
To give you a bit of context and feedback on this ticket:
I completely understand your point about not implementing all features of the MCP protocol. I came to the topic of resources because the Notion MCP regularly fails when trying to fetch the enhanced Markdown documentation. I inspected the Notion MCP and noticed that this documentation is a resource, but Bolt AI, or the LLM, tries to fetch it as a page instead. That results in an HTTP 400 error because Bolt AI doesn’t support resources.
That’s the main issue here. It makes the Notion integration quite buggy because the model doesn’t know about the Markdown features of Notion pages. As a result, it tries to create pages using the wrong syntax, which then fails.
I found a workaround by providing the content of that resource as a page in my Notion workspace and referencing it in the system prompt. That works, but it’s still just a workaround.
Just so you know how I came to this topic: I noticed that neither ChatGPT nor Claude has this issue. If you’re saying they don’t support resources either, then I think they must have found another workaround in their custom Notion integration.
Daniel Nguyen
Apr 28
I see. I’m not familiar with Notion, never liked them. Can you help me understand the issue better. For example, what I need to do in my brand new Notion account to replicate the issue you’re having. Maybe the bug was something else.
Claude does support many features of the MCP protocol since they invented it.
ChatGPT doesn’t. But they don’t need to because OpenAI has this private “connection” setup with their partners. I’m pretty sure they have private API etc to access Notion in this case.
I’ll try my best when I could replicate the issue. Supporting MCP resources might be the cleanest way to solve it actually.
Maximilian Christl
Apr 28
Hi @Daniel Nguyen,
i’m using
npx @modelcontextprotocol/inspectorto inspect the notion MCP. In the Create Page instructions you find this excerpt:IMPORTANT: For the complete Markdown specification, always first fetch the MCP resource at
notion://docs/enhanced-markdown-spec. Do NOT guess or hallucinate Markdown syntax. This spec is also applicable to other tools like update-page and fetch.So if you tell it to create a page it tries to fetch this via the page fetch, which won’t work.
Telling it to create a new Notion Page with sample content should be enough.
Atleast with OpenAI Models, 5.4 or 5.5 i’m able to reproduce this behavior consistently.