Activities of "alanlai"

[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:

1. 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.

2. 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).

3. 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.io and 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

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:

1. abp login <username> — succeeds ("Successfully logged in ... with the organization 'YID'")
2. 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:

1. Does the cloud MCP service require any entitlement beyond an active Business license (e.g., per-organization enablement)?
2. Can you check server-side logs for organization "YID" to see why the tool-definition fetch returns empty?
3. Is there a verbose/diagnostic flag for abp mcp to surface the underlying HTTP response?