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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

34 minutes ago