Niches · Databases & files

Give a team or non-engineers governed access through one server

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
7companies, fit with a limit
15companies carry the tag
7share of the category's work
7first-hand accounts

What counts as done

Each user connects with their own identity, queries run under that user's database rights, sources are named and described so the model picks the right one, and the connection works from the clients the team uses.

How agents ask for it: let the ops team ask the database questions in Claude, one server for all our databases, each person should only see their own data

Does the job, with a limit 7

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
MCP Toolbox for Databases A
Google LLC
Works as an OAuth 2.1 resource server validating JWTs, and BigQuery's useClientOAuth runs queries as the end user; other sources such as Postgres run under the one configured credential. source
MongoDB MCP Server A
MongoDB, Inc.
The hosted Atlas MCP server signs each user in with OAuth; the local server queries with the connection strings it was started with, shared by all callers. source
Neon MCP Server BB
Neon, LLC (subsidiary of Databricks, Inc.)
Each user authorises with OAuth and roleName pins SQL to a Postgres role, but SQL runs as the owner by default, and #333 shows ChatGPT's connector schema drifting from the hosted server. source
ObsessionDB F
Kellerkind UG (haftungsbeschränkt)
Each user signs in with OAuth 2.1 and a token sees only services in that user's organisations, but the docs do not say SQL runs under per-user database grants, and there is no read-only scope. source
PlanetScale MCP Server BB
PlanetScale, Inc.
Each caller authenticates with an OAuth2 access token or service token and queries use short-lived credentials minted per call, read from source; PlanetScale's own docs were not read because its website terms forbid automatic retrieval. source
Snowflake-managed MCP server C
Snowflake Inc.
Each user signs in with their own credentials through OAuth and RBAC governs each tool, with named, described tools, but there is no dynamic client registration, so an admin hands every client the integration's ID and secret. source
Supabase API + MCP BB
Supabase Pte. Ltd.
Each user signs in with OAuth and grants one organisation, but the docs do not say execute_sql runs under that user's database grants rather than the project's role. source

Doesn't do this job 10

Listings in the category that do something else, with the reason.

ListingWhy
Mirage (AgentVFS) B
Strukto.AI
Each mount holds one DSN or credential, and #16 shows sessions on one workspace sharing the whole mount tree. source
ClickHouse MCP Server BB
ClickHouse, Inc.
HTTP mode supports a bearer token or OAuth to the server, but every query runs as the one CLICKHOUSE_USER; #155 asks for per-user credentials with no answer. source
CoinMarketCap x402 API BB
CoinMarketCap
Not a server in front of the team's databases; payment per call is the authentication. source
DBHub BB
Bytebase
One instance holds one DSN per source and an optional shared bearer token; the maintainer told a user wanting per-user permissions to run one instance per user. source
Filesystem (MCP reference server) B
Model Context Protocol, a Series of LF Projects, LLC
A local stdio server for one person's folders; no per-user identity. source
Memory (MCP reference server) B
Model Context Protocol, a Series of LF Projects, LLC
A local stdio server; no users or identities.
Nansen x402 API B
Nansen
Not a server in front of the team's databases; payment per call is the authentication. source
Postgres MCP Pro F
Crystal Corp.
One DATABASE_URI per server process; no per-user identity or multi-source config in the README. source
Redis MCP C
Redis Ltd.
One connection from --url or flags per process; EntraID authenticates the server to Azure, not each user. source
ReqRes MCP server D
ReqRes
Project keys, not per-user identities in front of the team's databases. source

What stops agents finishing

  • client requires OAuth the server does not offer
  • server holds one set of credentials for everyone
  • client and server tool schemas drift apart

Around it

After: data.answer-question.

Where this comes from

Weight 7 of 100 in Databases & files: 7 of 52 accounts (DBHub multi-tenancy and staff use, ClickHouse per-user credentials, Neon ChatGPT connector, Mirage shared workspace)

The same as data: /api/v1/use-cases/data.team-access.json, or the MCP tool get_use_case with id data.team-access. Other jobs in this category: /api/v1/niches?category=data.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.