Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix MCP tools not accessible to main agent despite bundle-mcp configuration [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74726•Fetched 2026-04-30 06:20:42
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
2
Author
luuq2026luuq2026
Participants
clawsweeper[bot]clawsweeper[bot]luuq2026luuq2026mpalermitimpalermiti
Timeline (top)
cross-referenced ×3commented ×2closed ×1mentioned ×1

Fix Action

Fix / Workaround

MCP servers configured under mcp.servers are not accessible to the main OpenClaw agent. The built-in image tool always dispatches to the model provider, never to the MCP server.

Workaround: mmx vision describe works via shell exec.

RAW_BUFFERClick to expand / collapse

MCP servers configured under mcp.servers are not accessible to the main OpenClaw agent. The built-in image tool always dispatches to the model provider, never to the MCP server.

Environment: OpenClaw v2026.4.26, tools.profile: coding, mcp.servers configured and running.

The MCP server (minimax-coding-plan-mcp) IS healthy - responds to tools/list and returns web_search and understand_image.

Problem: image tool goes directly to Minimax API and fails with 2013 (no vision capability). Agent does not fall back to MCP understand_image tool.

Expected: Agent should use MCP understand_image when built-in image tool fails.

Workaround: mmx vision describe works via shell exec.

This is a follow-up to issue #74387 which was closed claiming already implemented.

extent analysis

TL;DR

The OpenClaw agent may need a configuration change to correctly route image tool requests to the MCP server when the built-in image tool fails.

Guidance

  • Verify that the mcp.servers configuration is correctly set up and the MCP server is running and responding as expected.
  • Check the OpenClaw agent's configuration to ensure it is set to use the MCP server as a fallback for image tool requests.
  • Investigate the difference in behavior between the mmx vision describe command, which works, and the built-in image tool, to identify potential configuration or implementation discrepancies.
  • Review the changes made in issue #74387 to ensure they were correctly implemented and did not introduce any regressions.

Notes

The issue may be related to a misconfiguration or an incomplete implementation of the fallback mechanism in the OpenClaw agent.

Recommendation

Apply a workaround by modifying the OpenClaw agent's configuration to correctly route image tool requests to the MCP server when the built-in image tool fails, as the root cause of the issue is not immediately clear.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#database connection#vector store#embedding generation#cache error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix MCP tools not accessible to main agent despite bundle-mcp configuration [2 comments, 3 participants]