Druid MCP Server

Connect Druid to Claude, Cursor or any other MCP client and it stops being a tab you switch to. AI-powered MCP server for Apache Druid cluster management and analytic. The druid mcp server is what makes that connection.

What the server does

A comprehensive Model Context Protocol (MCP) server for Apache Druid that provides extensive tools, resources, and prompts for managing and analyzing Druid clusters.

This MCP server implements a intend-based architecture where profiles picture their usaae intend and the corresponding area of Druid usage. The server provides three main types of MCP components:

• Spring AI MCP Server integration
• Tool-based architecture for MCP protocol compliance
• Tool-based Architecture — Complete MCP protocol compliance with automatic JSON schema generation
• Multiple Transport Modes — STDIO, SSE, and Streamable HTTP support including Oauth
• Real-time Communication — Server-Sent Events with streaming capabilities
• Comprehensive error handling

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Examples — The configuration includes multiple integration and transport options:
• Prerequisites — The Prerequisites tool exposed by this server
• Logging — The Logging tool exposed by this server

Installation

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

Credentials and setup notes

Configuration is passed through the environment: DRUID_ROUTER_URL, DRUID_AUTH_USERNAME, DRUID_AUTH_PASSWORD, DRUID_SSL_ENABLED, DRUID_SSL_SKIP_VERIFICATION, DRUID_COORDINATOR_URL, YOUR_JWT_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Java 25 - Maven 3.6+ - Apache Druid cluster running with router on port 8888

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Druid's toolset — Examples, Prerequisites, Logging — is a fair guide to whether it matches your workflow. It is maintained by com.iunera; worth a glance at recent repository activity before you build anything load-bearing on it.

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

Worth knowing first

• 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.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.