Tools

The Entropy Data MCP server exposes the following 9 tools.

Data Product Discovery

Get Data Product Details fetch

Get a data product by its ID. The data product contains all its output ports and server information. The response includes access status for each output port and inlines any data contracts.

Search Data Products search

Find and explore data products in the organization. Parameter:

• query: Keywords to search for in data product names/descriptions. Optional, use "*" to get all data products. Returns a list of data products with basic information, sorted by certification level (highest first). Includes certification name and rank if certified. You can fetch details later.

Strategy: First use a generic search term like "sales", "customers", "marketing" to find relevant data products. Use a more specific term if the results are too broad.

Access Management

Request Data Product Access request_access

Submit an access request for a specific data product's output port. This creates a formal request that may be automatically approved or require manual approval.

Parameters:

• dataProductId: The ID of the data product to request access to
• outputPortId: The ID of the output port within the data product
• purpose: Business justification for accessing the data
• roles: Optional list of role names to request (e.g., ["analyst", "data_engineer"]). Available roles can be found in the data contract's roles section, if any.

Returns information about the created access request including its ID, status, approval status, and requested roles.

Query Execution

Execute SQL Query execute_query

Execute SQL queries on data product output ports and query results as structured data (limited to 100 rows). Supports: Databricks, PostgreSQL, BigQuery, Snowflake, MySQL, MariaDB, SQL Server (MSSQL), Trino Must have active access to the output port and configured personal datasource connection.

The SQL should follow the datasource dialect. Try to use fully qualified table names when appropriate.

Data Contract Management

Get Data Contract datacontract_get

Get a data contract by its ID or external ID. Returns the complete data contract specification as originally defined.

The data contract can be in ODCS (Open Data Contract Standard) or DCS format.

Save Data Contract datacontract_save

EXPERIMENTAL. Save a data contract YAML specification. This will create a new data contract or update an existing one. The YAML must be valid ODCS (Open Data Contract Standard) or DCS format.

Get Data Contract Schema datacontract_schema

Get the JSON Schema for Open Data Contract Standard (ODCS). Returns the latest active schema - either the default ODCS schema or a custom organization-specific schema if defined.

This schema can be used for validating data contract specifications and understanding the structure of ODCS documents.

Get Data Contract Test Results datacontract_test_results

Get test results for a data contract. Returns the most recent test run results, optionally filtered by server name. Use the count parameter to retrieve older results (up to 20). Includes check outcomes (passed, failed, warning, error) and log messages.

Run Data Contract Test datacontract_test

Run a data contract test. Executes the configured data contract test against the specified server and returns the test results including individual check outcomes. Requires that Data Contract Tests are enabled and configured for the organization.