mentor tool listed in MCP manifest but returns 'tool does not exist' on remote HTTP transport

[denwx]

Environment

• Kiro version: 0.11.133+
• Transport: remote HTTP (https://mcp-test.datap-dev-us-east-1-01.dev-06.stamp.outsystemscloudrd.net/<tenant>/mcp)
• Tenant: eng-dev-us-10.outsystems.dev

Steps to reproduce

1. Install the odc-mcp Power and configure a tenant URL.
2. Call activate on the power — mentor appears in the tool list returned by the MCP server manifest.
3. Call mentor with a valid app_key and prompt.

Expected behavior

The mentor tool executes, downloads the OML for the app, and returns a mentor_session_id, mentor_session_token, and response.

Actual behavior

The server returns:

Tool 'mentor' does not exist on server 'power-odc-mcp-odc'.

Additional context

All read-only tools (context_*, app_*, env_*, deploy_*, extlib_*) work correctly over the HTTP transport. Only mentor (and likely publish_start / publish_status which depend on it) fails at call time despite being advertised in the manifest.

This suggests mentor is included in the tool manifest for the HTTP transport but the handler is not registered or enabled server-side for this transport type. The POWER.md notes that mentor requires a stdio CLI harness — it may be a known limitation of the HTTP transport or a misconfiguration.

[lucas-dbo]

I had this issue in dev with kiro as well.
Tested again today in kiro, stage, and it worked.