Thanks — the first three points are clear and useful, and the recommendation matches what our measurements pointed to, so the product decision is settled on our side.
Two questions remain open, and I would appreciate a review from the team: the reply came from AI-Bot and, on exactly these two points, states that no guidance is "documented" or "verified" rather than answering them.
Does anything inside ABP depend on the ExtraProperties column being a string-typed column? I am not asking whether overriding it is a supported customisation — you have answered that. I am asking what would actually break, so we can judge the risk ourselves. Specifically: ObjectExtensionManager, the audit log's property change tracking, distributed event serialisation, and the MongoDB provider.
Is provider-native JSON storage for ExtraProperties (SQL Server json, PostgreSQL jsonb) on your roadmap, or has it been considered and rejected? "Not planned" is a perfectly useful answer for us — we need to know whether to design around its absence permanently or treat it as a temporary gap.
Context, if useful: we are not looking for a workaround to push queryable data into ExtraProperties. We have accepted your recommendation and will keep query-critical dynamic attributes in an application-owned json column. Question 1 only matters for the smaller set of extended entities where the values already live in ExtraProperties today.
Thank you.
I have already performed these steps.
Environment:
ABP Studio Team Edition 10.4.1 Volo.Abp.Studio.Cli 3.0.4 Claude Code 2.1.169 MCP Inspector 0.22.0 Windows 11
I have already:
Updated Volo.Abp.Studio.Cli to 3.0.4.
Restarted ABP Studio.
Loaded the solution.
Verified that the AI Agent works correctly.
Tested both:
abp mcp-studio
and
abp mcp-studio --endpoint http://localhost:38271/mcp/
Reproduced the same problem with MCP Inspector, not only with Claude Code.
The bridge process stays alive, but the MCP handshake never completes.
MCP Inspector reports:
ZodError Invalid input: expected string/number, received null Unrecognized key: "error"
Therefore this does not appear to be a client-side issue.
Could you please escalate this to the ABP Studio team?
I can provide the complete MCP Inspector logs if necessary.
