MCP server for AnalyticDB MySQL via OpenAPI and direct SQL connection
Free
Nothing to run from here
Mongodb Lens is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MongoDB Lens: Full Featured MCP Server for MongoDB Databases
Quickstart
# 1 — run it from where its publisher ships it
npx -y mongodb-lens
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> MongoDB Lens: Full Featured MCP Server for MongoDB Databases
Publishernot claimed
FUAll 1 server
furey1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Mongodb Lens as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add mongodb-lens-mcp -- npx -y mongodb-lensReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
42 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Connect to a different MongoDB URI or alias
Takes no parameters.
Example callreturns →
Connect back to the original MongoDB URI used at startup
Takes no parameters.
Example callreturns →
Add a new MongoDB connection alias
Takes no parameters.
Example callreturns →
List all configured MongoDB connection aliases
Takes no parameters.
Example callreturns →
List all accessible MongoDB databases
Takes no parameters.
Example callreturns →
Get the name of the current database
Takes no parameters.
Example callreturns →
Create a new MongoDB database with option to switch
Takes no parameters.
Example callreturns →
Switch to a specific database
Takes no parameters.
Example callreturns →
Drop a database (requires confirmation)
Takes no parameters.
Example callreturns →
Create a new database user
Takes no parameters.
Example callreturns →
Drop an existing database user
Takes no parameters.
Example callreturns →
List collections in the current database
Takes no parameters.
Example callreturns →
Create a new collection with options
Takes no parameters.
Example callreturns →
Drop a collection (requires confirmation)
Takes no parameters.
Example callreturns →
Rename an existing collection
Takes no parameters.
Example callreturns →
Run validation on a collection to check for inconsistencies
Takes no parameters.
Example callreturns →
Get unique values for a field
Takes no parameters.
Example callreturns →
Run queries with filters and projections
Takes no parameters.
Example callreturns →
Count documents with optional filter
Takes no parameters.
Example callreturns →
Insert one or multiple documents into a collection
Takes no parameters.
Example callreturns →
Update specific documents in a collection
Takes no parameters.
Example callreturns →
Delete document(s) (requires confirmation)
Takes no parameters.
Example callreturns →
Run aggregation pipelines
Takes no parameters.
Example callreturns →
Create new index on collection
Takes no parameters.
Example callreturns →
Drop an existing index from a collection
Takes no parameters.
Example callreturns →
Get database or collection statistics
Takes no parameters.
Example callreturns →
Automatically infer schema from collection
Takes no parameters.
Example callreturns →
Generate a JSON Schema validator for a collection
Takes no parameters.
Example callreturns →
Compare schemas between two collections
Takes no parameters.
Example callreturns →
Analyze query performance
Takes no parameters.
Example callreturns →
Analyze query patterns and suggest optimizations
Takes no parameters.
Example callreturns →
Perform bulk inserts, updates, or deletes
Takes no parameters.
Example callreturns →
Create a time series collection for temporal data
Takes no parameters.
Example callreturns →
Find documents with language-specific collation rules
Takes no parameters.
Example callreturns →
Perform full-text search across text-indexed fields
Takes no parameters.
Example callreturns →
Run geospatial queries with various operators
Takes no parameters.
Example callreturns →
Execute multiple operations in a single transaction
Takes no parameters.
Example callreturns →
Watch for changes in a collection using change streams
Takes no parameters.
Example callreturns →
Manage large files with GridFS
Takes no parameters.
Example callreturns →
Clear memory caches to ensure fresh data
Takes no parameters.
Example callreturns →
Get sharding status for database or collections
Takes no parameters.
Example callreturns →
Export query results to formatted JSON or CSV
Takes no parameters.
Example callreturns →
Standardmost installed
$19 / month
- 16,000 calls a month, included
- 192 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Pro
$69 / month
- 160,000 calls a month, included
- 1,920 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $19 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 96 / 100
Release 9.1.4 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest283d739cf9ba067afff4fdeaa2029f4eeb12a05357d7d9bf1ef08179aecd7001
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (42 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| connect-mongodb | no tags | |
| connect-original | no tags | |
| add-connection-alias | no tags | |
| list-connections | no tags | |
| list-databases | no tags | |
| current-database | no tags | |
| create-database | no tags | |
| use-database | no tags | |
| drop-database | no tags | |
| create-user | no tags | |
| drop-user | no tags | |
| list-collections | no tags | |
| create-collection | no tags | |
| drop-collection | no tags | |
| rename-collection | no tags | |
| validate-collection | no tags | |
| distinct-values | no tags | |
| find-documents | no tags | |
| count-documents | no tags | |
| insert-document | no tags | |
| update-document | no tags | |
| delete-document | no tags | |
| aggregate-data | no tags | |
| create-index | no tags | |
| drop-index | no tags | |
| get-stats | no tags | |
| analyze-schema | no tags | |
| generate-schema-validator | no tags | |
| compare-schemas | no tags | |
| explain-query | no tags | |
| analyze-query-patterns | no tags | |
| bulk-operations | no tags | |
| create-timeseries | no tags | |
| collation-query | no tags | |
| text-search | no tags | |
| geo-query | no tags | |
| transaction | no tags | |
| watch-changes | no tags | |
| gridfs-operation | no tags | |
| clear-cache | no tags | |
| shard-status | no tags | |
| export-data | sensitive-source |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest283d739cf9ba067a
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 9.1.4 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
9.1.4
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Mongodb Lens in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.