MiniMax-AI / MiniMax-AI/MiniMax-Coding-Plan-MCP

[Bug] MCP tools fail with login fail even when API key is valid

Open
#22 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
102
Forks
30
PR merge metrics
No merged PRs in 30d

Description

问题描述

使用 minimax-coding-plan-mcp 时,web_search 和 understand_image 工具返回认证错误,但 API Key 实际上是有效的。

环境信息

  • MCP Server: minimax-coding-plan-mcp
  • Client: OpenClaw (使用 mcporter 调用)
  • OS: macOS
  • uvx 路径: 已确认可用

复现步骤

  1. 配置 MCP server 使用 Token Plan API Key
  2. 设置 MINIMAX_API_HOST=https://api.minimaxi.com (中国版)
  3. 调用 web_search 或 understand_image 工具

错误信息

API Error: login fail: Please carry the API secret key in the Authorization field of the request header, please check your API key and API host.

额外发现

  • 直接用 curl 调用 MiniMax API 可以成功(用同一个 API Key)
  • MCP server 本身在线(mcporter list 显示 2 tools, healthy)
  • 问题是 MCP server 内部调用 API 时认证失败

关联 Issue

  • #981: 类似的认证错误问题
  • #20: OpenClaw MCP 进程管理问题

可能原因

  1. MCP server 内部调用 API 的方式与直接 API 调用不同
  2. Token Plan 的 API 可能需要特殊的认证头或端点
  3. 可能是 OpenClaw mcporter 与 minimax-coding-plan-mcp 之间的兼容性问题

注意:这是通过 OpenClaw 的 mcporter 工具调用的,不是直接通过 Claude Desktop 或 Cursor

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the MCP server's internal API request and authentication path, then compare its headers and endpoint with the successful curl request described in the issue. Check the web_search and understand_image tool call paths. Done means both tools authenticate successfully with a valid Token Plan API key against the China API host.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, authentication, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.