DX MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_URL | Yes | Your database URL for connecting to DX Data Cloud |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listEntitiesB | List entities from the DX software catalog. Args: search_term (str, optional): Search term to filter by. type (str, optional): Filter entities by type (e.g., 'service', 'team', etc.). cursor (str, optional): Cursor for pagination. Get from response_metadata.next_cursor in prior requests. limit (int, optional): Number of entities per page - if present, must be between 1 and 50. |
| getEntityDetailsB | Get comprehensive details about a specific entity including its information, tasks, and scorecards - we can use this to check operational readiness/health of an entity. Args: identifier (str): The unique identifier for the entity (e.g., 'payment-processing'). |
| queryDataA | Execute a SQL query against the DX Data Cloud PostgreSQL database. Always query from information_schema if you are uncertain about which tables and columns to look at. Args: sql (str): SQL query to execute Returns: str: Formatted query results or error message |
| listInitiativesB | Lists all initiatives with summary information. Args: cursor (str, optional): Cursor for pagination. Get from response_metadata.next_cursor in prior requests. limit (int, optional): Limit the number of initiatives per page. Maximum 100, defaults to 50. published (bool, optional): Filter by published status. priority (int, optional): Filter by priority (0-2, lower numbers are more urgent). tags (str, optional): Comma-separated tags to filter by. |
| getInitiativeDetailsA | Get initiative details including both the initiative info and its progress report. Note: This calls two endpoints:
Args: id (str): Initiative public ID. entity_type_identifiers (str, optional): Passed through to initiatives.progressReport. limit (int, optional): Passed through to initiatives.progressReport. Maximum 100, defaults to 50. cursor (str, optional): Passed through to initiatives.progressReport. |
| listScorecardsB | List all active scorecards. Args: cursor (str, optional): Cursor for pagination. Get from response_metadata.next_cursor in prior requests. limit (int, optional): Limit the number of scorecards per page. Must be between 1 and 50. |
| getScorecardInfoA | Retrieve details about a specific scorecard, including its defined levels and checks. Args: id (str): The unique ID of the scorecard. |
| reviewTasksC | Review/resolve/complete outstanding DX tasks (failing checks). Args: entity_identifier (str): Entity identifier. check_ids (str): Comma-separated list of check IDs to focus on. |
| listTeamsB | List all teams in DX. |
| getTeamDetailsA | Retrieve details for an individual team. Note that searching by team_emails will return things like the team name and members, where the search by team_id/reference_id will return more detailed information about the team structure. Args: team_id (str, optional): The DX team ID. reference_id (str, optional): The team's internal reference ID in your organization. team_emails (str, optional): Comma separated list of team members' email addresses. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| reviewTasks | Review/resolve/complete outstanding DX tasks (failing checks). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have distinct purposes targeting different resources (entities, initiatives, scorecards, teams, tasks, and data queries), but getEntityDetails and getScorecardInfo could potentially overlap if scorecards are part of entity details. The descriptions clarify their focus, but there's minor ambiguity in the entity/scorecard relationship.
Tools follow a consistent verb_noun pattern (getEntityDetails, listEntities, etc.) with clear prefixes (get, list, query, review). The only deviation is queryData which uses 'query' instead of 'get' or 'list', but this is semantically appropriate for SQL execution, maintaining overall readability.
With 10 tools, the count is well-scoped for a DX software catalog and operational readiness server. Each tool serves a clear purpose in managing entities, initiatives, scorecards, teams, tasks, and data queries, avoiding bloat while covering essential operations.
The toolset provides good read/list coverage for entities, initiatives, scorecards, and teams, plus task review and data querying. However, there are notable gaps in write operations (e.g., no create/update/delete tools for these resources) and limited task management beyond review, which may hinder full lifecycle management in the domain.