›_ Claude Code Issues
Claude Code Issues / #48243

Notion plugin MCP server: persistent Internal Server Error after reinstall

Resolved 💬 21 comments Opened Apr 15, 2026 by geekybaiyi Closed May 25, 2026
💡 Likely answer: A maintainer (localden, collaborator) responded on this thread — see the highlighted reply below.

Description

The Notion plugin (notion@claude-plugins-official, v0.1.0) fails to connect with an "Internal Server Error" after multiple attempts to reconnect, re-authenticate, and reinstall.

Steps to Reproduce

  1. Notion plugin was working earlier in the session (tools like notion-search, notion-create-pages, notion-update-page all functioned correctly)
  2. After some time, the Notion MCP server disconnected
  3. Ran /mcp multiple times — Notion server fails to reconnect
  4. Uninstalled and reinstalled the plugin:

``
claude plugin uninstall notion@claude-plugins-official --scope user
claude plugin install notion@claude-plugins-official --scope user
``

  1. Ran /mcp again — still "Internal Server Error"
  2. The plugin shows as installed and enabled (claude plugin list confirms notion@claude-plugins-official, scope: user, status: enabled)

Environment

  • OS: macOS (Darwin 24.3.0)
  • Plugin: notion@claude-plugins-official v0.1.0
  • Scope: user
  • Other plugins working: Slack, Atlassian, Google Calendar all connect fine in the same session

Expected Behavior

Notion MCP server should reconnect and authenticate successfully after /mcp.

Actual Behavior

"Internal Server Error" on every connection attempt. No auth prompt appears — it fails before reaching authentication.

Additional Context

  • The Notion tools worked correctly earlier in the session for ~30+ API calls (search, create-pages, fetch, update-page)
  • The disconnect happened mid-session without any user action
  • Other MCP plugins (Slack, Atlassian, Google Calendar) remain connected and functional
  • Reinstalling the plugin did not resolve the issue

View original on GitHub ↗

21 Comments

metaWuming · 3 months ago

I suffer exactly same situation now and don't know how to fix it...

jackchien-jpg · 3 months ago

me too...

kelvin-mfv · 3 months ago

I have same issue, tried many times but still got error "Internal Server Error" at authentication step

stcjeve0018 · 3 months ago

same issue, pls fix it T_T

ryan-mf-chien · 3 months ago

me too.....

venkyqz · 3 months ago

same issue here...

judy00 · 3 months ago

same issue...

wisdom925 · 3 months ago

same issue here...

geekybaiyi · 3 months ago

I feel it's more a notion auth server bug? I also created the issue here
https://github.com/makenotion/claude-code-notion-plugin/issues/20

nagic0 · 3 months ago

same issue, this issue also occurs when I try to connect Notion with claude on https://claude.ai/settings/connectors

bjlinfunraise · 3 months ago

I get same error, my company can't use Notion MCP server through Claude.

<img width="376" height="158" alt="Image" src="https://github.com/user-attachments/assets/c6e9dd42-51af-4356-8671-ac0e5d1154ef" />

312581021ZongYingLee · 3 months ago

Same issue

marcdomancie · 3 months ago

Same issue

daniel840711 · 3 months ago

Same issue

guillaume-cauchet · 3 months ago

This is a pretty serious issue. Any sort of manual or automated workflow relying on notion becomes unusable.

addie-tyc · 3 months ago

<p>Same issue here — my failure happens slightly later in the flow (500 on <code>mcp.notion.com/callback</code> <em>after</em> I consent on notion.so, rather than before the auth prompt). Posting in case the root cause is shared.</p>

<p>Not familiar with OAuth protocols, but after some digging I found something that works:</p>

<pre><code>claude mcp add notion -s user -- npx -y mcp-remote https://mcp.notion.com/mcp
</code></pre>

<p>Observed behavior (didn't dig deep into why):</p>

Connection path | Result
-- | --
Plugin (notion@claude-plugins-official) | 500
claude.ai Notion connector | 500
mcp-remote bridge | Works

<p>One visible difference: <code>mcp-remote</code>'s callback URL has an <code>/oauth/</code> path prefix (<code>/oauth/callback</code>) while the failing paths go to <code>/callback</code> directly. Not sure if that's the actual cause, but it's the most obvious distinction I noticed.</p>

<p>Hope this helps someone.</p>

metaWuming · 2 months ago

Just found out that Notion's official open-source MCP server works — it's published by Notion itself, but instead of going through Claude Desktop's built-in connector, you install it from npm and wire it into Claude Desktop's config file yourself.
Steps:

Spin up @notionhq/notion-mcp-server with npx
Create an integration in Notion's settings and grab the token
Edit Claude Desktop's config file (claude_desktop_config.json) and add that server + token
Restart Claude Desktop
Share your Notion databases with the integration so it has access

Tested and working — my connection to Notion is fully back. If anyone else ran into the same disconnect issue, give it a try.

XIYINGDU · 2 months ago

me too

addie-tyc · 2 months ago

Plugin works now

kelvin-mfv · 2 months ago

With newest notion version, Mcp works now.

localden collaborator · 1 month ago

Thanks for the report. This and #48878 turned out to share the same root cause on our side, and the fix landed on May 21. That also explains why the plugin and the claude.ai connector failed while mcp-remote and integration-token setups kept working, and why some people saw it come and go in late April. Closing as fixed; please reopen if you still see the Internal Server Error on the Notion plugin after May 21.