cedardb vs GeoLens
cedardb is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
cedardb is a plugin bundle for AI coding tools published by CedarDB. No marketplace we read lists it any more. GeoLens is an MCP server published by geolens-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  GeoLens | |
|---|---|---|
| Community marketplace cedardb/claude-plugin | Removed on 2026-10-15 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.26.0 Downloads/month (PyPI): 1 135 Downloads/week (PyPI): 600 Forks (GitHub): 39 Stars (GitHub): 277 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 | cedardbno longer listed · | GeoLens |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | 277 |
| Forks (GitHub) (differs) | 0 | 39 |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (geolens-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 2 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cedardb/claude-plugin | github.com/geolens-io/geolens |
| Changes in the last 7 days (differs) | 2 | 3 |
| First seen (differs) | 2026-10-14 | 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 cedardb
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Ask your databases questions in plain English, run read-only SQL and set up data alerts.
-
Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite
-
Connect Claude to your SQL or MongoDB databases using GraphJin's schema-aware MCP server.
-
Safe, read-only-by-default MySQL, PostgreSQL & SQLite access for AI agents. TOON output.
-
Database management tools for Claude Code. Query databases, explore schemas, analyze data quality, and get optimization recommendations. Supports PostgreSQL, MySQL/MariaDB…
-
Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.
What each says it does
cedardb
Deploy, query, and visualize with the help of CedarDB directly from Claude Code.
GeoLens
Read-only access to a self-hosted GeoLens spatial catalog: datasets, features, maps, sandboxed SQL.
How to run each
cedardb
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
GeoLens As a local MCP server: PyPI package
claude mcp add --env "GEOLENS_API_KEY=<YOUR_GEOLENS_API_KEY>" --env "GEOLENS_INSTANCE=<YOUR_GEOLENS_INSTANCE>" --env "GEOLENS_TOKEN=<YOUR_GEOLENS_TOKEN>" --transport stdio geolens -- uvx geolens-mcpRequires: GEOLENS_API_KEY (secret), GEOLENS_INSTANCE, GEOLENS_TOKEN (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 cedardb publish no settings it asks for, so we do not compare settings.
What it can do: cedardb · What it can do: GeoLens · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.