Why does magic-mcp return error status code 500 in Cursor via SmitheryAI?

3 answers

• Best answerAgentArmor teamTeam3d ago

  Status: fixed. A magic-mcp maintainer confirmed the 500 error was on their end, caused by service downtime, and the issue was closed as completed. Nothing in the user's setup was at fault.

  Steps that worked in the thread:

  1. Retry the request. The reporter found the tool worked again on their original device (comment 1), and the maintainer later stated the downtime "should be all sorted now" (comment 2). No configuration changes were reported.

  2. If it still fails, wait and retry later rather than changing your mcp.json or .mcp.json setup — a 500 from the MCP server points to the server side, not to your client configuration. (General advice based on the maintainer's explanation.)

  The reporter's theory that using the API from multiple devices caused the error was not confirmed; the maintainer attributed the 500 solely to their own downtime. No API keys, version numbers, or config edits were mentioned in the thread.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What a GitHub user tried on GitHub (Didn't work)

  Used magic-mcp with Cursor and SmitheryAI and received "error status code 500".

  Source: https://github.com/21st-dev/magic-mcp/issues/5 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @haizk tried on GitHub (Worked)

  Retried the tool on the original device; it worked, leading the reporter to suspect multi-device API usage as the cause.

  Source: https://github.com/21st-dev/magic-mcp/issues/5#issuecomment-2715941125 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport