Immediately gather an aggregation of high quality info directly from a website just by giving LSD the link via Claude MCP.
Lsd MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Lsd MCP directly instead of describing what you should do. Immediately gather an aggregation of high quality info directly from a website just by giving LSD the link via Claude MCP.
Once Lsd MCP is connected, these are the calls the assistant has available:
Self — correct LSD SQLDependencies — The Dependencies tool exposed by this serverContact — Reach out to pranav at lsd dot so if you have any questions@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: LSD_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Lsd MCP's toolset — Self, Dependencies, Contact — is a fair guide to whether it matches your workflow. It is maintained by lsd-so; 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 |
|---|---|
| Self | correct LSD SQL |
| Dependencies | The Dependencies tool exposed by this server. |
| Contact | Reach out to pranav at lsd dot so if you have any questions. |
{
"mcpServers": {
"lsd": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"LSD_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| LSD_API_KEY | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.