Environment:
- ABP CLI (Volo.Abp.Studio.Cli): 3.0.6 (also reproduced on a fresh install of the latest version, currently the same 3.0.6)
- OS: Ubuntu (Docker container on WSL2, Windows 11); also reproduced in a clean
mcr.microsoft.com/dotnet/sdk:10.0 container
- License: Business (organization: YID), login verified via
abp login-info
- We have reviewed /docs/latest/studio/model-context-protocol and confirmed we are using
abp mcp (cloud service), not abp mcp-studio; there appears to be no dedicated documentation page for abp mcp itself.
Steps to Reproduce:
abp login <username> — succeeds ("Successfully logged in ... with the organization 'YID'")
- Run
abp mcp
Expected: local MCP server starts in stdio mode and waits for client handshake.
Actual:
Checking extensions...
[MCP][ERROR] Error running MCP server | Exception: CliUsageException
Error: Failed to fetch tool definitions from ABP.IO MCP Server. No tools available. The MCP server cannot start without tool definitions.
Process exits immediately (exit code 0). MCP clients (Claude Code) report Failed to reconnect: -32000.
What we've ruled out:
- Network: abp.io → HTTP/2 200; mcp.abp.io → HTTP/2 405 (endpoint reachable)
- Authentication: correct user/organization;
abp logout + fresh login — same error
- Token staleness: fresh login on a brand-new container — same error
- CLI version: fresh latest install in clean SDK container, extensions downloaded OK — same error
- Transient outage: consistently reproducible across multiple days
abp mcp get-config works and returns the standard stdio configuration
Questions:
- Does the cloud MCP service require any entitlement beyond an active Business license (e.g., per-organization enablement)?
- Can you check server-side logs for organization "YID" to see why the tool-definition fetch returns empty?
- Is there a verbose/diagnostic flag for
abp mcp to surface the underlying HTTP response?