gopls-lazy-lsp vs Grain SQL
gopls-lazy-lsp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑02.
gopls-lazy-lsp is a plugin bundle for AI coding tools published by izumin5210. No marketplace we read lists it any more. Grain SQL is an MCP server published by pattrnlabs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Grain SQL | |
|---|---|---|
| Community marketplace izumin5210/dotfiles | Removed on 2026-11-02 Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.10.49 Downloads/month (npm): 5 170 Downloads/week (npm): 2 284 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.10.49 Downloads/month (npm): 5 170 Downloads/week (npm): 2 284 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | gopls-lazy-lspno longer listed · | Grain SQL |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 22 | 3 |
| Forks (GitHub) | 1 | 1 |
| Last release (differs) | Not published | 2026-11-05 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (grain-tools) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/izumin5210/dotfiles | github.com/pattrnlabs/grain |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-22 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of gopls-lazy-lsp
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
gopls-lsp
Go language server for code intelligence and refactoring
-
Go language server for code intelligence and refactoring
-
Semantic Go code analysis using gopls — type-aware definitions, references, implementations, and call hierarchy.
-
Gleam language server integration (bundled with the Gleam compiler)
-
Intlayer language server: Go-to-Definition for useIntlayer / getIntlayer / useDictionary / getDictionary keys across all *-intlayer packages
-
Go development tools: gopls MCP server, LSP integration, automatic gofmt formatting, golangci-lint linting, CVE dependency patching, Go stdlib CVE triage, and OCP and OKD release…
What each says it does
gopls-lazy-lsp
Go language server using the gopls-lazy proxy
Grain SQL
Run SQL queries and inspect database schemas through safe, visible MCP tools.
How to run each
gopls-lazy-lsp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Grain SQL As a local MCP server: npm package
claude mcp add --env "GRAIN_CONNECTIONS=<YOUR_GRAIN_CONNECTIONS>" --transport stdio grain -- npx -y grain-toolsRequires: GRAIN_CONNECTIONS (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of gopls-lazy-lsp publish no settings it asks for, so we do not compare settings.
What it can do: gopls-lazy-lsp · What it can do: Grain SQL · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.