Catalog, scorecard, initiative and team tools cover the structured questions, and queryData is the way out when a question has no endpoint shaped for it — arbitrary SQL against DX Data Cloud, the only tool here whose scope is not fixed by the API it wraps. reviewTasks is the sole tool that changes anything; everything else reads. getInitiativeDetails combines initiatives.info and initiatives.progressReport, so status and progress arrive together.
An MCP server for a DX instance — software catalog, scorecards, initiatives, teams, and a SQL endpoint onto DX Data Cloud
- Catalog reads: listEntities with a search term and type filter, getEntityDetails for one entity together with its tasks and scorecards.
- Scorecards — the active set, and one scorecard's levels and checks in full.
- reviewTasks resolves the outstanding DX tasks on an entity, which are its failing checks.
- Initiatives filtered by priority, tag and published state, and getInitiativeDetails, which returns the initiative record and its progress report from a single call.
- Team lookup by team_id, reference_id or member emails, where the email route returns name and members and the id route returns the fuller team structure.
- queryData executes SQL against the DX Data Cloud PostgreSQL database, with information_schema there when the table layout is unknown.
A DX instance with a populated software catalog, plus access to its DX Data Cloud PostgreSQL database for queryData.
One command plus a key — pip install dx-mcp-server, then supply credentials