openclaw - 💡(How to fix) Fix MCP tools not accessible to main agent — only to embedded Pi/coding sessions [3 comments, 3 participants]

TL;DR

To make MCP tools accessible to the main OpenClaw agent, consider modifying the configuration to expose MCP servers to the main agent tool dispatch layer.

Guidance

• Review the proposed solutions (Option A, B, C) and assess their feasibility for your specific use case.
• If a direct configuration change is not possible, evaluate the current workaround using shell exec to call mmx CLI directly, understanding its limitations and potential security implications.
• Investigate the openclaw.json configuration file to understand how mcp.servers definitions are currently being used and how they might be extended or modified to support main agent access.
• Consider the trade-offs between directly exposing MCP tools to the main agent versus maintaining the current abstraction layer for model interactions.

Example

No specific code example is provided due to the lack of detailed implementation information in the issue.

Notes

The solution may depend on the specific requirements and constraints of the OpenClaw agent and its interaction with MCP servers. Directly exposing MCP tools to the main agent could introduce complexity or security risks that need to be carefully evaluated.

Recommendation

Apply a workaround, such as using the shell exec method to call mmx CLI directly, until a more integrated solution can be implemented, as it provides an immediate, albeit temporary, fix to the accessibility issue of MCP tools.