Dremio MCP server

Created By
dremioa year ago
Dremio MCP server
Overview

What is Dremio MCP Server?

Dremio MCP Server is a Model Context Protocol server designed to facilitate the integration of Large Language Models (LLMs) with Dremio, enhancing data interaction and analysis capabilities.

How to use Dremio MCP Server?

To use the Dremio MCP Server, clone the repository, install the required Python package, and configure the server and LLM settings before running the server.

Key features of Dremio MCP Server?

  • Simplified integration of LLMs with Dremio.
  • Configurable server modes for different use cases.
  • Support for multiple LLMs, currently including Claude.

Use cases of Dremio MCP Server?

  1. Enabling LLMs to analyze and discover patterns in data.
  2. Facilitating workload analysis through introspection of Dremio systems.
  3. Connecting to Prometheus for enhanced insights and metrics.

FAQ from Dremio MCP Server?

  • What is the purpose of the MCP server?

The MCP server eases the integration of LLMs with Dremio, allowing for advanced data analysis and interaction.

  • What configurations are needed?

You need to set up both the server config file and the LLM config file to connect and communicate effectively.

  • Is Dremio MCP Server open source?

Yes, it is open source and encourages contributions from the community.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dremio
Star
21
Language
Python
License
Apache-2.0 license
Tags

Recommend Servers

View All
Voyei

3 hours 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.

13 hours ago