Apache Doris MCP Server

Created By
morningmana year ago
An MCP server for Apache Doris & VeloDB
Overview

What is Apache Doris MCP Server?

Apache Doris MCP Server is a server designed for Apache Doris, which implements the Model Context Protocol (MCP) to facilitate data management and processing.

How to use Apache Doris MCP Server?

To use the server, set up the environment with the required parameters and run the command using the provided cursor setup. You can also run the MCP Inspector for development purposes.

Key features of Apache Doris MCP Server?

  • Implements Model Context Protocol for efficient data handling
  • Supports integration with Apache Doris
  • Provides a development environment for testing and publishing

Use cases of Apache Doris MCP Server?

  1. Managing data workflows in Apache Doris.
  2. Developing and testing data processing applications.
  3. Publishing data models using the MCP framework.

FAQ from Apache Doris MCP Server?

  • What is the Model Context Protocol?

The Model Context Protocol is a standard for managing and processing data models in a consistent manner.

  • Is there a specific environment required to run the server?

Yes, you need to install the 'uv' package and set up the environment variables as specified in the usage instructions.

  • Can I contribute to the development of Apache Doris MCP Server?

Yes, contributions are welcome! You can find the repository on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
morningman
Star
3
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
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)

20 hours ago
Gpt Scrambler

2 days ago