Overview
Features
MCP-compatible server surface
Provides an MCP-compliant server that exposes Alation context capabilities to MCP clients.
Dual transport modes (STDIO and HTTP)
Supports both STDIO for direct MCP connections and HTTP for web/API integrations.
Remote MCP Server deployment
Allows running the MCP service remotely without local SDK installation; connect to a remote endpoint after a one-time authorization.
Dynamic tool discovery and lazy resolution
Dynamically lists tools based on user permissions and lazily resolves tools to minimize version drift.
Streaming support
All MCP tools support streaming; enable with sdk_options(enable_streaming=True) and iterate over results.
Chat ID integration
Supports passing chat_id in tool calls and includes chat_id in responses to link related interactions.
Predefined MCP tool set
Includes a curated set of MCP tools (e.g., alation_context, bulk_retrieval, check_job_status, data_quality_tool, get_custom_fields_definitions, get_data_products, get_data_sources_tool, get_signature_creation_instructions, lineage, update_catalog_asset_metadata).
Dynamic API contracts and version resilience
Tool contracts can be dynamic to minimize client-server version mismatches and reduce brittleness during upgrades.
Who Is This For?
- MCP Clients:Expose Alation catalog context to MCP-enabled agents and applications for contextual reasoning.
- Data Engineers:Integrate catalog context into data workflows via MCP for richer runtime decisions.
- AI Agents:Leverage MCP server to reason over catalog metadata within agent workflows.




