# Reported issues for notion-mcp-server Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [notion-mcp-server](/mcp/notion-mcp-server). ## Most discussed ### Thanks! (and a collection of fixes) Hey! Thanks for the MCP server, especially the atomicity, response slimming, and markdown-first support everywhere. I've run this on my own test case and identified a bunch of issues, from minor usability (S3 URLs #50) to security (file upload from anywhere #51). I've had my Claude submit each fix as a minimal PR with tests, but I'm QCing them and hand-writing the PR description before releasing them as ready. Let me know if there's anything I can do to help with these. [Read the thread](https://github.com/awkoy/notion-mcp-server/issues/54) · 2026-07-29 · open · outside contributor · 2 comments ### Feature Request: View-based database querying Thanks for building this MCP and making it free and open sourced! The typed `where` DSL and batch operation support already make it the best Notion MCP server I've tried, not to mention other cool features. One gap I'm running into: **database views**. Currently the server handles pages and databases well, but views are not really supported. ### Proposed operations 1. **Query a view's data rows by its id** — execute a view's filters/sorts/groupings and return the resulting rows. 2. **CRUD on [Read the thread](https://github.com/awkoy/notion-mcp-server/issues/18) · 2026-06-20 · closed · outside contributor · 1 comment ### Configure allowlisted operations Hi! Would it be possible to add an operation allowlist in this project? It'd be pretty useful IMO Something like a env `NOTION_ALLOWED_OPERATIONS` with comma-separated operations would be enough [Read the thread](https://github.com/awkoy/notion-mcp-server/issues/7) · 2026-06-03 · closed · external user · 3 comments ### archive_page and restore_page use deprecated archived field instead of in_trash ## Summary `notion_pages` actions `archive_page` and `restore_page` currently call `notion.pages.update()` with the deprecated `archived` request body field. With newer Notion API versions, this fails with a validation error because Notion now expects `in_trash` instead. ## Current behavior Calling `archive_page` with a valid page ID returns a Notion validation error similar to: ```text Error: The request body does not match the schema for the expected parameters (validation_error) ``` The [Read the thread](https://github.com/awkoy/notion-mcp-server/issues/6) · 2026-05-19 · closed · external user · 0 comments ### Unexpected token 'o', "notion-mcp-"... is not valid JSON 2025-05-06T23:07:34.079Z [notion-mcp-server] [error] Unexpected token 'o', "notion-mcp-"... is not valid JSON {"context":"connection","stack":"SyntaxError: Unexpected token 'o', \"notion-mcp-\"... is not valid JSON\n at JSON.parse ()\n at F$e (C:\\Users\\ivan\\AppData\\Local\\AnthropicClaude\\app-0.9.3\\resources\\app.asar\\.vite\\build\\index.js:108:189)\n at j$e.readMessage (C:\\Users\\ivan\\AppData\\Local\\AnthropicClaude\\app-0.9.3\\resources\\app.asar\\.vite\\build\\inde [Read the thread](https://github.com/awkoy/notion-mcp-server/issues/2) · 2025-05-06 · closed · external user · 2 comments ### Context too large. I constantly get the context too large once I have added the MCP server to cursor. I'm only using the notion MCP. Image Image Image Cursor version: 0.48.7 [Read the thread](https://github.com/awkoy/notion-mcp-server/issues/1) · 2025-04-07 · closed · external user · 2 comments ## Most recent The remaining reports are on [the project's issue tracker](https://github.com/awkoy/notion-mcp-server/issues).