A MCP server with Mimer Database Connectivity
Most database access work still happens through a UI a human drives. Mimer MCP server moves it into the conversation instead. A MCP server with Mimer Database Connectivity.
A Model Context Protocol (MCP) server that provides Mimer SQL database connectivity to browse database schemas, execute read-only queries with parameterization support, and manage stored procedures.
The server publishes 9 tools. What each one is for:
list_schemas — List all available schemas in the databaselist_table_names — List table names within the specified schemaget_table_info — Get detailed table schema and sample rowsexecute_query — Execute SQL query with parameter support (Only SELECT queries are allowed)list_stored_procedures — List read-only stored procedures in the databaseget_stored_procedure_definition — Get the definition of a stored procedureget_stored_procedure_parameters — Get the parameters of a stored procedureexecute_stored_procedure — Execute a stored procedure in the database with JSON parametersPrerequisites — The Prerequisites tool exposed by this serverConfiguration is passed through the environment: DOTENV_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mimer's toolset — list_schemas, list_table_names, get_table_info and 6 more — is a fair guide to whether it matches your workflow. It is maintained by mimersql; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_schemas | List all available schemas in the database |
| list_table_names | List table names within the specified schema |
| get_table_info | Get detailed table schema and sample rows |
| execute_query | Execute SQL query with parameter support (Only SELECT queries are allowed) |
| list_stored_procedures | List read-only stored procedures in the database |
| get_stored_procedure_definition | Get the definition of a stored procedure |
| get_stored_procedure_parameters | Get the parameters of a stored procedure |
| execute_stored_procedure | Execute a stored procedure in the database with JSON parameters |
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"mcpServers": {
"mimer": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"DOTENV_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DOTENV_PATH | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.