Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix MCP server tools missing from agent request body — regression still present in v2026.4.27 [1 comments, 2 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#76063•Fetched 2026-05-03 04:42:42
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
luuq2026luuq2026
Participants
clawsweeper[bot]clawsweeper[bot]luuq2026luuq2026
Timeline (top)
commented ×1unsubscribed ×1

MCP server tools are not included in the agent's outbound request body in v2026.4.27. The regression was marked as fixed in v2026.4.27 but testing confirms the issue persists. v2026.4.27 also introduces silent confabulation as the failure mode, more dangerous than the honest failure in v2026.4.26.

Root Cause

Root cause hypothesis

RAW_BUFFERClick to expand / collapse

Summary

MCP server tools are not included in the agent's outbound request body in v2026.4.27. The regression was marked as fixed in v2026.4.27 but testing confirms the issue persists. v2026.4.27 also introduces silent confabulation as the failure mode, more dangerous than the honest failure in v2026.4.26.

Environment

  • OpenClaw: v2026.4.27 (commit cbc2ba093146)
  • Node.js: v22.x
  • Tool profile: coding
  • MCP servers: 2x stdio servers (verified healthy, returning 50+ tools total)

Expected vs Actual

  • v2026.4.26: agent reports honestly — "I don't have access to those tools"
  • v2026.4.27: agent silently fabricates plausible output (e.g. fabricated inbox content). No MCP tool definitions in request body.

Evidence

Token count ~48-49k per request (bundled tools only). MCP tool definitions would add 20-30k tokens. Request body contains only: edit, exec, image, process, read, session_status, sessions_*, subagents, web_fetch, web_search, write. No server__* MCP tools.

Root cause hypothesis

Commit c4e5ca86 (fix, merged 2026-04-22) may have been narrowed by commit fc6cfbd418 ("fix(agents): honor bundle mcp tool allowlist", 2026-04-26) before the release tag was created.

Request

  1. Confirm regression still present in v2026.4.27
  2. Identify which commit introduced the narrowing
  3. Confirm whether c4e5ca86 actually reached v2026.4.27 release
  4. Provide a fix commit we can validate

Related

  • #74844 (closed incorrectly)
  • #74726 (duplicate)
  • #74387 (original, closed as "already implemented")

extent analysis

TL;DR

The issue can be resolved by reverting or adjusting the changes introduced in commit fc6cfbd418 to ensure that MCP server tools are included in the agent's outbound request body.

Guidance

  • Review the changes made in commit fc6cfbd418 and assess how it may have narrowed the fix introduced in commit c4e5ca86, potentially causing the regression.
  • Verify that commit c4e5ca86 is indeed included in the v2026.4.27 release by checking the release notes or the commit history.
  • Test the agent with the c4e5ca86 commit applied to confirm whether it resolves the issue of MCP server tools not being included in the request body.
  • Consider creating a new fix commit that reverts or adjusts the changes in fc6cfbd418 to ensure compatibility with the original fix.

Example

No code snippet is provided as the issue does not contain sufficient code details.

Notes

The root cause of the issue seems to be related to the interaction between commits c4e5ca86 and fc6cfbd418. The exact fix may depend on the specifics of these commits and how they affect the inclusion of MCP server tools in the agent's request body.

Recommendation

Apply a workaround by reverting the changes in commit fc6cfbd418 until a proper fix can be implemented and validated, as this commit seems to be the likely cause of the regression.

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…
#container setup#orchestration issue#cache issue#memory leak#API versioning

Still need to ship something?

×6

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

Back to top recommendations

TRENDING