
Mimer Mcp
io.github.mimersqlPublished by GitHub account mimersqlv1.0.5Updated Oct 24, 2026
An MCP server with Mimer SQL Database Connectivity
Overview
Connects an assistant to a Mimer SQL database to browse schemas, run read-only SELECT queries, and inspect or execute stored procedures.
- What you can do
- Provides tools to list schemas and table names, get table schema details with sample rows, and run parameterized SQL queries where only SELECT statements are allowed. It also lists read-only stored procedures, retrieves their definitions and parameters, and executes them with JSON parameters. Connection pooling options control how many database connections are opened and reused.
- When to use it
- Useful when an assistant needs to explore or query a Mimer SQL database, for example to answer questions about schema structure, inspect sample data, or call existing stored procedures. It fits read-oriented analysis rather than general database administration.
- Requirements
- Runs locally as a Python package (Python 3.10+ with uv) or via Docker; a Mimer SQL 11.0+ instance must be reachable. Requires DB_DSN, DB_USER and DB_PASSWORD, plus optional DB_HOST, DB_PORT, DB_PROTOCOL, connection pool settings and MCP_LOG_LEVEL, typically supplied through a .env file.
Installation
In SourceWeft
- Open Mimer Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Mimer MCP Server
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.
Available Tools
Database Schema Tools
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 rows
Query Execution Tools
execute_query— Execute SQL query with parameter support (Only SELECT queries are allowed)
Stored Procedure Tools
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 parameters
Getting Started
Prerequisites
- Python 3.10 or later (with uv installed) or Docker
- Mimer SQL 11.0 or later
Environment Configuration
Before running the server, you need to configure your database connection settings using environment variables. The Mimer MCP Server reads these from a .env file.
Mimer MCP Server can be configured using environment variables through .env file with the following configuration option:
Usage with VS Code
MCP servers are configured using a JSON file (mcp.json). Different MCP hosts may have slightly different configuration formats. In this guide, we'll focus on VS Code as an example. First, ensure you've installed the latest version of VS Code and have access to Copilot.
One way to add MCP server in VS Code is to add the server configuration to your workspace in the .vscode/mcp.json file. This will allow you to share configuration with others.
- Create a
.vscode/mcp.jsonfile in your workspace. - Add the following configuration to your
.vscode/mcp.jsonfile, depending on how you want to run the MCP server.
Option 1: Using Docker (Recommended)
Option 1.1: Build the Docker Image Locally
Then, add the following configuration to .vscode/mcp.json file
Option 1.2: Use the Pre-Built Image from Docker Hub
Option 1.3: Use Docker compose and the official Mimer SQL docker container
This will start a Mimer SQL Docker container as well as the mimer-mcp-server container,
set up a private network between the two containers and create the Mimer SQL example database.
The Mimer SQL database will be stored in the docker volume called mimer_mcp_data so that database changes are persistent.
Option 2.1: Using uvx
Option 2.2: Using uv
- After saving the configuration file, VS Code will display a Start button in the
mcp.jsonfile. Click it to launch the server.
- Open Copilot Chat and in the Copilot Chat box, select Agent mode from the dropdown.
- Select the Tools button to view the list of available tools. Make sure the tools from Mimer MCP Server are selected.
- Enter a prompt in the chat input box and notice how the agent autonomously selects a suitable tool, fix errors and generate a final answer from gathered queries results. (Following examples use the Example Database from Mimer, which is owned by MIMER_STORE. Read more about this database: here)
Development
Prerequisites
- Python: 3.10+
- uv: for dependency management and running the server
- Mimer SQL 11.0 or later
- Node.js and npm: for debugging with MCP inspector
Install uv:
Verify installation:
Install Node.js and npm:
Verify installation:
Getting Started
-
Clone the repository
-
Create and activate a virtual environment
- Install dependencies from pyproject.toml
- Configure environment variables
The configuration is loaded automatically via config.py.
Debug with MCP inspector
MCP Inspector provides a web interface for testing and debugging MCP Tools (Requires Node.js: 22.7.5+):
Note: MCP Inspector is a Node.js app and the npx command allows running MCP Inspector without having to permanently install it as a Node.js package.
Alternatively, you can use FastMCP CLI to start the MCP inspector
To run the Mimer SQL docker image and mimer-mcp-server using Docker compose, run:
or to run it as a daemon:
This way it is possible to call the mimer-mcp-server using HTTP and port 3333.
Source: README.md at commit d21a0c0
Tools
0Version history
1- v1.0.5LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts