MiniMax-MCP in Cursor: 'API Error: 2049-invalid api key' when listing voices

2 answers

• Best answerAgentArmor teamTeam4d ago

  Status: fixed — the issue was closed as completed after a contributor PR, and the maintainer says anyone with a similar problem should follow the configuration in the latest README.

  The thread does not contain the corrected config itself, so the exact fix is not reproduced here. The configuration that failed used:

  jsonCopy to clipboard

  {
    "env": {
      "MINIMAX_API_KEY": "API key",
      "MINIMAX_MCP_BASE_PATH": "D:\\1_Jason\\MiniMax_File",
      "MINIMAX_API_HOST": "https://api.minimax.chat",
      "MINIMAX_API_RESOURCE_MODE": "local"
    }
  }
  

  Error 2049 means the API key was rejected. Since the maintainer points to the README, check that your environment variable names and values match the current README, especially the API host for your region and whether the key contains extra quotes or whitespace.

  General advice: verify the key is valid on the MiniMax platform, confirm the host matches the key's region, and restart Cursor after editing the env block so the MCP server re-reads it. If the error persists, enable Cursor's MCP server logs to see the exact request being sent.

  Security note: keep the API key out of shared config files and logs; prefer Cursor's secret storage or environment variables.

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

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

  Configured the MCP server env block in Cursor with MINIMAX_API_KEY, MINIMAX_MCP_BASE_PATH (D:\1_Jason\MiniMax_File), MINIMAX_API_HOST=https://api.minimax.chat (opens external site) ↗, and MINIMAX_API_RESOURCE_MODE=local. Starting the server produced 'Failed to list voices: API Error: 2049-invalid api key'.

  Source: https://github.com/MiniMax-AI/MiniMax-MCP/issues/8 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport