console-mcp-server version 1.3.0-rc.5 get_configuration tool returns bad results when ref provided is a version (rather than a revision)

[alexevansvu]

What product would you like to leave feedback for?

Marketplace

What Console version are you using?

v14.5.5

Description

When retrieving project configuration by version tag the MCP toolreturns a response with nearly all configuration fields empty, even though the same version should have complete configuration data. Notably, revisions return correctly populated configuration fields

Steps to Reproduce

1. Call configuration_get with a valid projectId and a version tag
2. Compare the response against the same data retrieved using a revision

Expected Behavior

Configuration retrieved by version should contain the same populated fields as configuration retrieved by revision, including:

• endpoints
• collections
• services
• applications
• groups
• secrets
• cmsCategories
• Environment-specific variables and configuration

Actual Behavior

Configuration retrieved by version returns with nearly all fields empty:
{
"endpoints": {},
"collections": {},
"groups": [],
"secrets": [],
"cmsCategories": {},
"services": {},
"applications": {},
"apiVersions": [],
"unsecretedVariables": [],
// ... other empty structures
}

Only the cmsSettings and fastDataConfig fields contain data.

Impact

• Users of the MCP server cannot inspect configuration at specific version tags
• Version comparison workflows using the MCP are broken

Workaround
Viewing versions within the Mia Console works just fine, this is only an issue with the mia mcp server

[albertotessarotto]

Thanks for reporting,
We'll investigate the issue and schedule a fix.
We'll keep you updated as soon as we have any progress to share.