lightdash-mcp-server

Created By
syucreama year ago
A MCP(Model Context Protocol) server that accesses to Lightdash
Overview

What is lightdash-mcp-server?

lightdash-mcp-server is a Model Context Protocol (MCP) server that provides access to Lightdash's API, enabling AI assistants to interact with Lightdash data through a standardized interface.

How to use lightdash-mcp-server?

To use lightdash-mcp-server, install it via npm, configure your Lightdash API credentials in a .env file, and start the server using the provided commands.

Key features of lightdash-mcp-server?

  • MCP-compatible access to Lightdash's API
  • Tools for listing projects, spaces, charts, and dashboards
  • Ability to retrieve custom metrics and catalogs
  • Support for running examples and development scripts

Use cases of lightdash-mcp-server?

  1. Integrating AI assistants with Lightdash for data analysis.
  2. Automating project management tasks within Lightdash.
  3. Accessing and manipulating Lightdash data programmatically.

FAQ from lightdash-mcp-server?

  • How do I install lightdash-mcp-server?

You can install it using npm with the command: npm install lightdash-mcp-server.

  • What do I need to configure?

You need to create a .env file with your Lightdash API key and URL.

  • Can I run examples?

Yes! You can run example scripts provided in the examples directory after setting the required environment variables.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
syucream
Star
17
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago