Lightdash MCP Server

A MCP(Model Context Protocol) server that accesses to lightdash( https://www.lightdash.com/ )

Local serverstdio

What is the Lightdash MCP server?

A MCP(Model Context Protocol) server that accesses to lightdash( https://www.lightdash.com/ ). That is what the lightdash mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

This server provides MCP-compatible access to Lightdash's API, allowing AI assistants to interact with your Lightdash data through a standardized interface.

  • list_projects - List all projects in the Lightdash organization
  • get_project - Get details of a specific project
  • list_spaces - List all spaces in a project
  • list_charts - List all charts in a project
  • list_dashboards - List all dashboards in a project
  • get_custom_metrics - Get custom metrics for a project

Getting it running

@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • Installation — The Installation tool exposed by this server
  • Configuration — The Configuration tool exposed by this server
  • Usage — The lightdash-mcp-server supports two transport modes: Stdio (default) and HTTP
  • Contributing — 1. Fork the repository 2. Create your feature branch 3. Run tests and linting: npm run lint 4. Commit your changes 5. Push to the branch 6. Create a

What it needs from you

Configuration is passed through the environment: LIGHTDASH_API_KEY, LIGHTDASH_API_URL. 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.

Things to watch

  • 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.

How it compares

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. Lightdash's toolset — Installation, Configuration, Usage and 1 more — is a fair guide to whether it matches your workflow. It is maintained by syucream; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
InstallationThe Installation tool exposed by this server.
ConfigurationThe Configuration tool exposed by this server.
UsageThe lightdash-mcp-server supports two transport modes: **Stdio** (default) and **HTTP**.
Contributing1. Fork the repository 2. Create your feature branch 3. Run tests and linting: npm run lint 4. Commit your changes 5. Push to the branch 6. Create a Pull Request

How to install the Lightdash MCP server

{
  "mcpServers": {
    "lightdash-1": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "LIGHTDASH_API_KEY": "your-value",
        "LIGHTDASH_API_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LIGHTDASH_API_KEYCredential the server authenticates with.Yes
LIGHTDASH_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Lightdash to Installation.
  • Use Lightdash to Configuration.
  • Use Lightdash to Usage.

Frequently asked questions

It connects Lightdash to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Installation, Configuration, Usage, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Lightdash directly.