A
licenseNot graded
qualityD
maintenanceImplements the Model Context Protocol for managing, ingesting, and querying structured and unstructured data with integration to graph databases, vector search, and LLMs.
3
MIT
MCP Server for OpenMetadata
by yangkyeongmo
Related Servers
Alternatives to MCP Server for OpenMetadata
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables type-safe, bidirectional communication with Model Context Protocol services, allowing centralized management of model contexts over HTTP.209MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying and managing Redash data sources, queries, dashboards, alerts, and users through the Model Context Protocol.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Smartsheet API to search, retrieve, create, update, and manage sheets, rows, webhooks, sharing permissions, cross-sheet references, and perform bulk operations through the Model Context Protocol.161 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceExposes Swagger/OpenAPI-defined APIs through the Model Context Protocol, making them accessible to AI agents.11 npmISC
- AlicenseBqualityDmaintenanceExposes RSpace API endpoints to LLM agents using the Model Context Protocol.91Apache 2.0
TDQS
C2.6/5.0
Scored across 186 tools
Disambiguation4/5
Each tool targets a distinct resource/action, and get_X vs get_X_by_name pairs are explicitly differentiated by ID vs FQN in their descriptions. The main risk is the sheer number of similar entity-specific getters (database, dashboard, database_service), but descriptions resolve most ambiguity.
Naming Consistency5/5
Tool names follow a strong, predictable snake_case action_resource pattern: list_<entity>, get_<entity>, get_<entity>_by_name, create_<entity>, update_<entity>, delete_<entity>. Domain actions like test_service_connection, add_lineage, and validate_policy still fit the verb-first convention clearly.
Tool Count1/5
186 tools is an extreme surface for a single MCP server, far beyond the 25+ threshold where selection quality collapses. Even with consistent naming, this flat catalog is overwhelming and would be better split into domain-specific servers for metadata, quality, governance, and search.
Completeness3/5
Core metadata entities such as tables, databases, schemas, dashboards, topics, metrics, users, and teams have full or near-full CRUD coverage. However, significant gaps remain: dashboard services and messaging services lack update/delete operations, and glossary terms only have list/get and no create/update/delete lifecycle.
Maintenance
ActivityInactive
ResponsivenessUnresponsive