Alation Agent SDK with MCP support
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"alation-ai-agent-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP Integration The SDK includes built-in support for the Model Context Protocol (MCP), which enables AI models to retrieve knowledge from Alation during inference. This package provides an MCP server that exposes Alation Data Catalog capabilities to AI agents with support for multiple transport modes. ## New Major Version 1.x.x #### Oct 23, 2026 Update `1.0.0` is the first stable release of the Alation AI Agent SDK. - Requests now send an `Ai-Surface` header (default `sdk`); set `AgentSDKOptions(surface=...)` to identify your integration - The MCP server requires `certifi>=2026.10.19`, and its Docker image refreshes the OS CA store, removing trust in the compromised eMudhra intermediate CAs - Auth parameter objects redact secrets in their `repr()` - Streaming and non-streaming responses handle malformed or empty payloads more gracefully #### Jan 14, 2026 Update `1.0.0rc3` version of the Alation AI Agent SDK is now available. - Added `get_context_by_id` tool for semantic catalog search with custom signatures - Removed `update_catalog_asset_metadata` and `check_job_status` tools - Upgraded fastMCP to address security vulnerability - Tool refactoring and endpoint updates #### Dec 10, 2025 Update `1.0.0rc2` version of the Alation AI Agent SDK is now available. It deprecates the Context Tool in favor of the more capable Catalog Context Search Agent. On the practical side, Catalog Context Search Agent shares the same contract so any migrations should be straightforward. We've committed to keep the now deprecated Context Tool as part of the SDK for the next **three months for transition**. This means you should expect to see it **removed in Feb 2026**. The main rationale for removing the Context Tool originates from having two tools which do very similar things. When both are exposed to an LLM, the model often picks the less capable one leading to worse outcomes. By reducing the number of tools that overlap conceptually, we're avoiding the wrong tool selecti…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.