Is this different from listing tables?

Yes. Listing databases returns the databases on a server; listing tables returns the tables inside one database. An agent usually lists databases first to pick the right one, then lists that database's tables before it writes a query.

What does an agent do with the list?

It picks a target. A server can hold many databases, so the agent reads the list, chooses the one that holds the data it needs, and scopes its next call, listing tables or running a query, to that database.

MCP servers that can list databases

4 verified servers expose a tool that can list databases on a server

A database server often hosts many databases, and an agent has to know which exist before it queries one. Listing databases returns them, so the agent picks the right one to run a query against or to inspect its tables.

These verified servers let an agent list the databases on a server or cluster.

Top pick

ClickHouse

Official

ClickHouse's official MCP server lets agents list databases and tables and run read-only SQL against a ClickHouse cluster.

databases793

Tool:

list_databases

ClickHouse can hold many analytical databases on one cluster, and list_databases returns them so an agent can pick the one to query.

Pick 2

CockroachDB

amineelkouhen

Community

A natural-language MCP server for CockroachDB: query data, manage schema, and monitor cluster health across nodes.

databases10

Tool:

list_databases

On a CockroachDB cluster, list_databases enumerates the databases the connection can reach, the step before inspecting tables or running SQL.

Pick 3

Metabase

Cognition

Community

A maintained Metabase MCP server from Cognition that lets an agent run questions, build dashboards, and query databases across your Metabase instance.

data-analytics57

Tool:

list_databases

Metabase sits in front of your data connections, so list_databases returns the databases it is wired to, the catalog an agent picks a query target from.

Pick 4

InfluxDB

InfluxData

Official

InfluxData's official MCP server lets an agent write, query, and manage time-series data in InfluxDB 3 using SQL and line protocol.

databases32

Tool:

list_databases

InfluxDB's list_databases returns the available time-series databases on the host, for an agent working with metrics data.

What to know

Listing databases is the first step into a server an agent does not already know. A ClickHouse cluster, a CockroachDB instance, an InfluxDB host can each hold many databases, and the agent needs the name before it lists tables or runs a query. The tools return the databases the connection can see; from there the agent drills into one. It is also how an agent confirms it is pointed at the right server, and which databases that connection actually exposes.

The set of databases on a server is stable, so an agent that maps out the layout once can hold it rather than re-list every session. Remembering which database holds which kind of data lets it go straight to the right one instead of re-enumerating the server each time it needs to query.

Questions

Is this different from listing tables?: Yes. Listing databases returns the databases on a server; listing tables returns the tables inside one database. An agent usually lists databases first to pick the right one, then lists that database's tables before it writes a query.
What does an agent do with the list?: It picks a target. A server can hold many databases, so the agent reads the list, chooses the one that holds the data it needs, and scopes its next call, listing tables or running a query, to that database.