A MCP(Model Context Protocol) server that accesses to lightdash( https://www.lightdash.com/ )
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.
This server provides MCP-compatible access to Lightdash's API, allowing AI assistants to interact with your Lightdash data through a standardized interface.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 4 tools. What each one is for:
Installation — The Installation tool exposed by this serverConfiguration — The Configuration tool exposed by this serverUsage — The lightdash-mcp-server supports two transport modes: Stdio (default) and HTTPContributing — 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 aConfiguration 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.
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.
| Tool | What it does |
|---|---|
| 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 Pull Request |
{
"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.
| Variable | Description | Required |
|---|---|---|
| LIGHTDASH_API_KEY | Credential the server authenticates with. | Yes |
| LIGHTDASH_API_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.