You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MCP server is not running properly when tested locally. Additionally, when attempting to mount it on a client site using Uvicorn, it results in an Internal Server Error (500). However, when tested with MCP Inspector and Claude Desktop, the server appears to be running correctly.
Steps to Reproduce
Run the MCP server locally.
Verify its functionality using MCP Inspector and Claude Desktop (works fine).
Attempt to mount the server on a client site using Uvicorn.
Observe the Internal Server Error (500) response.
Expected Behavior
The MCP server should run properly when mounted on a client site using Uvicorn.
API requests should not result in Internal Server Errors.
Actual Behavior
The server runs successfully in MCP Inspector and Claude Desktop.
When mounted using Uvicorn, the client site returns an Internal Server Error (500).
Environment Details
Python Version: 3.13.2
Package Manager: uv
MCP Framework: FastMCP
Deployment Setup:
Local Testing (Working: MCP Inspector, Claude Desktop)
Client-Side Mounting via Uvicorn (Error: Internal Server Error 500)
Logs & Error Messages
(Include any relevant logs, traceback, or console output here.)
Possible Causes Considered
The server itself is running fine in other environments.
The issue may be related to Uvicorn configuration or an incompatibility with MCP.
Database connection issues or missing environment variables.
Additional Context
If there are any configuration files, Uvicorn command-line options, or deployment settings that may be relevant, include them here.
Suggested Debugging Steps
Verify Uvicorn logs for additional details.
Check database connections and environment variables.
Run Uvicorn in verbose/debug mode to identify specific error causes.
Test with a different ASGI server (e.g., Daphne, Hypercorn) to check if the issue persists.
Action Required
Requesting assistance in debugging the issue and identifying why the MCP server fails under Uvicorn but works in other environments.
Activity
MrXnneHang commentedon Jul 14, 2025
I meet this too, once I ran the app in uvicorn, it always shows connection closed.
It may due to the transports?
MrXnneHang commentedon Jul 14, 2025
https://medium.com/@wilson.urdaneta/taming-the-beast-3-lessons-learned-integrating-fastmcp-sse-with-uvicorn-and-pytest-5b5527763078
see here
felixweinberger commentedon Oct 3, 2025
Thanks for reporting this issue! Closing this as likely addressed here.
Should this still be an issue please open a new issue and provide a code snippet we can run to debug on our end!
nguyenbs commentedon Aug 6, 2026
The connector is still failing. Both authenticated identity and repository checks return MCP -32603 Internal error:
This is still a connector backend/session problem, not a repository permission error.