Skip to main content
Glama
pfldy2850

mcp-openmetadata

by pfldy2850

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENMETADATA_URIYesThe OpenMetadata server URI
OPENMETADATA_PASSWORDNoPassword for basic authentication
OPENMETADATA_USERNAMENoUsername for basic authentication
OPENMETADATA_JWT_TOKENNoJWT token for token authentication

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_entities_with_queryC

Search entities using query test. Use query params from and size for pagination. Use sort_field to sort the results in sort_order.

get_table_by_fqnC

Get a table by fully qualified table name.

get_sample_dataC

Get sample data from a table.

get_table_owners_by_fqnB

Get a table owners by fully qualified table name.

get_table_columns_by_fqnC

Get a table columns by fully qualified table name.

get_list_of_tablesC

Get a list of tables, optionally filtered by database it belongs to. Use fields parameter to get only necessary fields. Use cursor-based pagination to limit the number entries in the list using limit and before or after query params.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: search across entities, retrieve a table, fetch sample data, fetch owners, fetch columns, and list tables. While get_table_by_fqn may return columns as part of the entity, the specific getters are explicitly focused, so an agent can select based on need without confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (get_* and search_*), use lowercase with underscores, and are uniformly structured. There are no mixed conventions or vague verbs.

Tool Count5/5

With 6 tools, the server is well-scoped for a metadata browsing purpose. Each tool provides a distinct capability without redundancy or excessive granularity, fitting comfortably within the ideal range.

Completeness3/5

The server covers core table read operations (get, list, columns, owners, sample data) and a general entity search. However, it lacks direct retrieval for other metadata entities like databases, schemas, and tags, and has no create/update/delete operations, which are common in metadata management. This leaves notable gaps for a full OpenMetadata surface.

Maintenance

ActivityInactive
ResponsivenessNo issues