Does a project mean a database here?

On Supabase, Neon, and MongoDB Atlas, roughly yes: a project is the container a database or cluster lives in. On Plane it is a planning space for tasks. The list call is the same idea on each: return the projects so an agent can pick the id it then operates on.

Why list projects before acting?

To get the id and to avoid the wrong target. The action tools reference a project by id, and on database platforms running against the wrong project is how an agent breaks production. Listing first lets it confirm which project it means before it queries or migrates.

MCP servers that can list projects

4 verified servers expose a tool that can list projects on a platform

A project is the container the rest of the work sits in, so before an agent operates on one it usually lists them: which databases exist, which planning spaces, which it is allowed to touch. Listing projects returns that set so the agent picks the right id to act on.

These verified servers let an agent list the projects on a platform.

Top pick

Supabase

Supabase (community)

Community

Connects agents to a Supabase project: run SQL, inspect schema, read logs, and manage edge functions.

databases2,710

Tool:

list_projects

Supabase's list_projects returns every project on the account, the inventory of databases an agent can then query, branch, or inspect.

Pick 2

Neon

Official

Neon's official MCP server lets agents create projects and branches, run SQL, and drive safe schema migrations on serverless Postgres.

databases606

Tool:

list_projects

On Neon, list_projects returns the account's projects with summaries, so an agent can find the serverless Postgres it means to work on.

Pick 3

Plane

Official

Plane's official MCP server exposes its full project API — work items, cycles, modules, and more — to agents.

project-management235

Tool:

list_projects

Plane's list_projects returns the planning spaces in a workspace, the lookup before an agent files or lists work items in the right one.

Pick 4

MongoDB

Official

MongoDB's official MCP server: query and manage databases, plus Atlas cluster administration.

databases1,039

Tool:

atlas-list-projects

atlas-list-projects lists the Atlas projects that clusters and access rules hang off, the grouping an agent resolves before it touches a cluster.

What to know

Project means a different unit on each platform, which the list reflects. On Supabase and Neon a project is a provisioned database, so the list is the agent's inventory of databases it can query or branch. On MongoDB Atlas it is the grouping clusters live under. On Plane it is a planning space for work items. The list resolves a human name to the project id the other tools want, and it is how an agent confirms a project exists before running anything against it.

The set of projects changes slowly, so an agent that maps a name to its id once can hold that rather than re-list every session. For database platforms this also bounds risk: knowing exactly which projects exist, and which are production, keeps an agent from running a migration against the wrong one.

Questions

Does a project mean a database here?: On Supabase, Neon, and MongoDB Atlas, roughly yes: a project is the container a database or cluster lives in. On Plane it is a planning space for tasks. The list call is the same idea on each: return the projects so an agent can pick the id it then operates on.
Why list projects before acting?: To get the id and to avoid the wrong target. The action tools reference a project by id, and on database platforms running against the wrong project is how an agent breaks production. Listing first lets it confirm which project it means before it queries or migrates.