A
license-
qualityC
maintenanceEnables AI agents to search, explore data lineage, understand business context, and generate SQL queries across an organization's data ecosystem.
Apache 2.0
Sidecar
Server Details
Cross-tool context for your data stack. Search, lineage, and impact across warehouse and BI tools.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.9/5.0
Tool DescriptionsA
Average 4.3/5 across 10 of 10 tools scored. Lowest: 3.3/5.
Server CoherenceA
Disambiguation3/5
There are overlapping tool pairs: advanced_search vs resolve_asset_id (both find assets), calculate_downstream_impact vs inspect_lineage_details (both trace lineage), and describe_asset vs resolve_asset_id (both provide details). While descriptions help clarify distinct use cases, an agent could still be confused about which to call, especially for lineage and asset retrieval.
Naming Consistency4/5
Nine of ten tools follow a verb_noun pattern (e.g., get_catalog_overview, describe_asset). The exception is 'advanced_search', which uses an adjective instead of a verb, breaking the pattern. This minor inconsistency does not significantly impair usability.
Tool Count5/5
With 10 tools, the server is well-scoped for a data catalog. Each tool serves a distinct purpose in searching, describing, and analyzing data assets and lineage, without being overly numerous or sparse.
Completeness4/5
The tool set covers core catalog operations: asset search, lookup, detailed descriptions, lineage tracking, downstream impact analysis, and knowledge base access. Minor gaps exist, such as the lack of a full asset listing tool and absence of knowledge base search within files, but these are not critical for typical workflows.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityBmaintenanceData observability for AI agents. Query alerts, monitor freshness, investigate schema drift, and trace lineage across your data warehouse via 53 MCP tools.1MIT
- Alicense-qualityCmaintenanceEnables AI agents to query live schema, lineage, and query-context across data warehouses, dbt projects, orchestration systems, and BI tools via MCP tools.Apache 2.0
- Alicense-qualityCmaintenanceEnables AI agents to understand and query your database safely by providing a semantic layer of metadata, with tools to search, explain, validate, and generate safe SQL.2MIT