Documentation Index
Fetch the complete documentation index at: https://openmetadata-feat-feat-2mbfixtestexui.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
OpenMetadata MCP Tools Reference
Overview
This document provides detailed examples and usage patterns for all available OpenMetadata MCP tools. Each tool includes sample requests, responses, and common use cases.
Description: Find data assets and business terms in your OpenMetadata catalog.
Use Cases:
- Discover tables containing specific data
- Find dashboards related to business areas
- Search for glossary terms
- Locate pipelines by name or description
Parameters
| Parameter | Type | Required | Description |
|---|
query | string | Yes | Keywords to search for |
entity_type | string | No | Filter by entity type (table, topic, dashboard, etc.) |
limit | integer | No | Max results to return (default: 10) |
fields | string | No | Comma-separated additional fields to include |
Entity Types
- Service Entities: databaseService, messagingService, apiService, dashboardService, pipelineService, storageService, mlmodelService, metadataService, searchService
- Data Asset Entities: apiCollection, apiEndpoint, table, storedProcedure, database, databaseSchema, dashboard, dashboardDataModel, pipeline, chart, topic, searchIndex, mlmodel, container
- User Entities: user, team
- Domain Entities: domain, dataProduct
- Governance Entities: metric, glossary, glossaryTerm
Examples
Basic Search:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_metadata",
"arguments": {
"query": "sales"
}
}
}
Search for Specific Entity Type:
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "search_metadata",
"arguments": {
"query": "customer",
"entity_type": "table",
"limit": 15
}
}
}
Search with Additional Fields:
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "search_metadata",
"arguments": {
"query": "order",
"entity_type": "table",
"fields": "columns,queries,upstreamLineage",
"limit": 5
}
}
}
Sample Response:
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"content": [
{
"type": "text",
"text": "Found 5 results matching 'sales':\n\n**Tables:**\n1. **sales_transactions** (mysql_prod.ecommerce.public.sales_transactions)\n - Description: Daily sales transaction records\n - Service: mysql_prod (MySQL)\n - Owners: sales-team, john.doe@company.com\n - Tags: PII, Financial\n - [View in OpenMetadata](https://your-om.com/table/mysql_prod.ecommerce.public.sales_transactions)\n\n2. **sales_reports** (postgresql_analytics.reporting.main.sales_reports)\n - Description: Aggregated sales reporting data\n - Service: postgresql_analytics (PostgreSQL)\n - Owners: analytics-team\n - [View in OpenMetadata](https://your-om.com/table/postgresql_analytics.reporting.main.sales_reports)\n\n**Dashboards:**\n3. **Sales Performance Dashboard** (looker_prod.sales.sales_performance)\n - Description: Real-time sales KPI dashboard\n - Service: looker_prod (Looker)\n - Charts: 8 charts\n - [View in OpenMetadata](https://your-om.com/dashboard/looker_prod.sales.sales_performance)"
}
]
}
}
2. get_entity_details
Description: Retrieve detailed information about a specific entity using its fully qualified name.
Parameters
| Parameter | Type | Required | Description |
|---|
entity_type | string | Yes | Type of entity (table, topic, dashboard, etc.) |
fqn | string | Yes | Fully qualified name of the entity |
Examples
Get Table Details:
{
"jsonrpc": "2.0",
"id": 4,
"method": "tools/call",
"params": {
"name": "get_entity_details",
"arguments": {
"entity_type": "table",
"fqn": "mysql_prod.ecommerce.public.customer_orders"
}
}
}
Get Dashboard Details:
{
"jsonrpc": "2.0",
"id": 5,
"method": "tools/call",
"params": {
"name": "get_entity_details",
"arguments": {
"entity_type": "dashboard",
"fqn": "superset_prod.sales.quarterly_revenue"
}
}
}
Sample Response:
{
"jsonrpc": "2.0",
"id": 4,
"result": {
"content": [
{
"type": "text",
"text": "## Table: customer_orders\n\n**Fully Qualified Name**: mysql_prod.ecommerce.public.customer_orders\n\n**Basic Information**:\n- **Service**: mysql_prod (MySQL)\n- **Database**: ecommerce\n- **Schema**: public\n- **Type**: Regular Table\n- **Description**: Stores all customer order transactions with order details, timestamps, and status information\n\n**Ownership & Governance**:\n- **Owners**: ecommerce-team, sarah.johnson@company.com\n- **Tags**: PII, Financial, Customer-Data\n- **Tier**: Tier1\n\n**Schema** (5 columns):\n1. **order_id** (BIGINT) - Primary key, unique order identifier\n2. **customer_id** (BIGINT) - Foreign key to customer table\n3. **order_date** (TIMESTAMP) - When the order was placed\n4. **total_amount** (DECIMAL) - Total order value\n5. **status** (VARCHAR) - Order status (pending, completed, cancelled)\n\n**Usage Statistics**:\n- **Row Count**: ~2.5M rows\n- **Size**: 450 MB\n- **Last Updated**: 2024-01-15 09:30:00\n\n[View in OpenMetadata](https://your-om.com/table/mysql_prod.ecommerce.public.customer_orders)"
}
]
}
}