mcp-server-openmetadata

Created By
tpaveleka year ago
Overview

What is mcp-server-openmetadata?

The mcp-server-openmetadata is a Model Context Protocol (MCP) server implementation for OpenMetadata, designed to facilitate seamless integration with MCP clients. It provides a standardized way to interact with OpenMetadata through the Model Context Protocol.

How to use mcp-server-openmetadata?

To use the mcp-server-openmetadata, set up the server by configuring the necessary environment variables for authentication, and then run the server using the provided commands. You can also integrate it with Claude Desktop or run it manually using Python.

Key features of mcp-server-openmetadata?

  • Implements the Model Context Protocol for OpenMetadata.
  • Provides a REST API for various data assets, services, teams, users, and more.
  • Supports both token and basic authentication methods.
  • Allows for manual execution and configuration.

Use cases of mcp-server-openmetadata?

  1. Integrating OpenMetadata with various data management tools.
  2. Facilitating data asset management through a standardized API.
  3. Enabling seamless communication between MCP clients and OpenMetadata.

FAQ from mcp-server-openmetadata?

  • What is the Model Context Protocol?

The Model Context Protocol is a standardized protocol for interacting with metadata services, allowing for consistent communication between clients and servers.

  • How do I authenticate with the server?

You can authenticate using either token authentication or basic authentication by setting the appropriate environment variables.

  • Can I run the server manually?

Yes, you can run the server manually using the command python src/server.py.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tpavelek
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago