Gravitino MCP Server

MCP server providing Gravitino APIs - A FastMCP integration for Apache Gravitino services. The gravitino mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

• Seamless integration with FastMCP for Gravitino APIs
• Simplified interface for metadata interaction
• Supports metadata operations for catalogs, schemas, tables, models, users, tags, and user-role management

Its toolset

Everything the assistant can do here goes through one of these:

• get_list_of_catalogs — Retrieve a list of catalogs
• get_list_of_schemas — Retrieve a list of schemas
• get_list_of_tables — Retrieve a paginated list of tables
• get_table_by_fqn — Fetch detailed information for a specific table
• get_table_columns_by_fqn — Retrieve column information for a table
• get_list_of_tags — Retrieve all tags
• associate_tag_to_entity — Attach a tag to a table or column
• list_objects_by_tag — List objects associated with a specific tag
• get_list_of_roles — Retrieve all roles
• get_list_of_users — Retrieve all users
• grant_role_to_user — Assign a role to a user
• revoke_role_from_user — Revoke a user's role

Configuration

You will need 6 environment variables: GRAVITINO_URI, GRAVITINO_USERNAME, GRAVITINO_PASSWORD, GRAVITINO_METALAKE, GRAVITINO_JWT_TOKEN, YOUR_GRAVITINO_JWT_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Gravitino's toolset — get_list_of_catalogs, get_list_of_schemas, get_list_of_tables and 11 more — is a fair guide to whether it matches your workflow. It is maintained by datastrato; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Gravitino's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Gravitino.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the gravitino mcp server does with a few real requests.