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.0container - 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), notabp mcp-studio; there appears to be no dedicated documentation page forabp mcpitself.
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-configworks 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 mcpto surface the underlying HTTP response?
3 Answer(s)
-
0
- Your post doesn’t include any error/log output, so a definitive “why it fails” can’t be derived from the provided info.
- If by “ABP MCP” you mean MCP servers in ABP Studio / ABP AI Agent, the most common verified causes/fixes are:
Update ABP Studio
- ABP Studio 2.1.9 includes: “Fixed MCP server CLI output problem.”
- So if your MCP server process starts but Studio can’t read/parse its output (looks like “fails to start”), upgrading to that or newer is the first action.
If you upgraded ABP to 10.4 and MCP broke
- ABP 10.4 includes MCP server integration enhancements specifically affecting stdio transport and workspace relationships.
- After upgrading, re-test the MCP server connection and tool listing (some configs may need adjustment depending on your setup).
If “fails to start” is actually an auth/network block inside Studio
- Corporate security software can block ABP Studio’s outbound network calls (a real-world confirmed case was Kaspersky restrictions).
- Ensure
abp.ioand its subdomains are reachable/allowlisted.
Sources (validated)
- https://abp.io/docs/10.4//studio/release-notes
- https://abp.io/docs/10.4//release-info/migration-guides/abp-10-4
- https://abp.io/community/articles/trb9o4ev
If this is a license / ABP Studio account-type issue on your environment, please contact us at: https://abp.io/contact
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
[AI-Bot] said:
- Your post doesn’t include any error/log output, so a definitive “why it fails” can’t be derived from the provided info.
- If by “ABP MCP” you mean MCP servers in ABP Studio / ABP AI Agent, the most common verified causes/fixes are:
Update ABP Studio
- ABP Studio 2.1.9 includes: “Fixed MCP server CLI output problem.”
- So if your MCP server process starts but Studio can’t read/parse its output (looks like “fails to start”), upgrading to that or newer is the first action.
If you upgraded ABP to 10.4 and MCP broke
- ABP 10.4 includes MCP server integration enhancements specifically affecting stdio transport and workspace relationships.
- After upgrading, re-test the MCP server connection and tool listing (some configs may need adjustment depending on your setup).
If “fails to start” is actually an auth/network block inside Studio
- Corporate security software can block ABP Studio’s outbound network calls (a real-world confirmed case was Kaspersky restrictions).
- Ensure
abp.ioand its subdomains are reachable/allowlisted.
Sources (validated)
- https://abp.io/docs/10.4//studio/release-notes
- https://abp.io/docs/10.4//release-info/migration-guides/abp-10-4
- https://abp.io/community/articles/trb9o4ev
If this is a license / ABP Studio account-type issue on your environment, please contact us at: https://abp.io/contact
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
It didn’t solve my problem
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi,
On the licensing question first: an active Business license is enough. There's no separate MCP entitlement, license tier, or feature toggle for the cloud MCP server, so this isn't a per-organization enablement gap on the license side.
The "No tools available" message means the CLI did get a response back, but couldn't read any tool definitions out of it. To see what's actually coming back for your organization, could you grab two things. Run them inside the same container/shell where
abp mcpfails, so we're looking at the exact~/.abp/cliconfig that command uses (running it elsewhere would read a different config):- The MCP config file, in case a custom server URL is set there (it overrides the endpoint the CLI talks to).
- The raw HTTP response from the tool-definitions endpoint, using your logged-in token.
-iincludes the status line so we can see the exact status code and body (the response itself doesn't contain your token).
cat ~/.abp/cli/mcp-config.json 2>/dev/null || echo "no custom config" TOKEN=$(sed $'s/\xef\xbb\xbf//' ~/.abp/cli/access-token.bin) curl -i -H "Authorization: Bearer $TOKEN" https://mcp.abp.io/toolsIf you also run the CLI directly on Windows and hit the same error there, the PowerShell equivalent is:
Get-Content "$HOME\.abp\cli\mcp-config.json" -ErrorAction SilentlyContinue $token = (Get-Content "$HOME\.abp\cli\access-token.bin" -Raw).Trim() curl.exe -i -H "Authorization: Bearer $token" https://mcp.abp.io/toolsThat output tells us whether the endpoint is returning an empty list, a redirect, or an auth/license rejection — three very different things to chase.
Two notes:
abp mcp get-configonly prints the local stdio config and never calls the server, so it working doesn't tell us anything about this endpoint. And theABP_MCP_LOG_LEVELenv var is capped at info level in the released CLI and won't print the raw HTTP response, so the curl above is the quicker way to capture it.We'll check the server-side logs for your organization in parallel. Send those two outputs over and we'll pin it down.
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)