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.
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
execute_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 parameters
- Python 3.10 or later (with uv installed) or Docker
- Mimer SQL 11.0 or later
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:
| Environment Variable | Default | Description |
|---|---|---|
DB_DSN |
Required | Database name to connect to |
DB_USER |
Required | Database username |
DB_PASSWORD |
Required | Database password |
DB_HOST |
- | Database host address (use host.docker.internal for Docker) |
DB_PORT |
1360 |
Database port number |
DB_PROTOCOL |
tcp |
Connection protocol |
DB_POOL_INITIAL_CON |
0 |
Initial number of idle connections in the pool |
DB_POOL_MAX_UNUSED |
0 |
Maximum number of unused connections in the pool |
DB_POOL_MAX_CON |
0 |
Maximum number of connections allowed (0 = unlimited) |
DB_POOL_BLOCK |
false |
Determines behavior when exceeding the maximum number of connections. If true, block and wait for a connection to become available; if false, raise an error when maxconnections is exceeded |
DB_POOL_DEEP_HEALTH_CHECK |
true |
If true, validates connection health before getting from pool (slower but more reliable) |
MCP_LOG_LEVEL |
INFO |
Logging level for the MCP server. Options: DEBUG, INFO, WARNING, ERROR, CRITICAL |
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.
docker build -t mimer-mcp-server .Then, add the following configuration to .vscode/mcp.json file
{
"servers": {
"mimer-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--add-host=host.docker.internal:host-gateway",
"--env-file=/absolute/path/to/.env",
"mimer-mcp-server",
]
}
},
"inputs": []
}{
"servers": {
"mimer-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--add-host=host.docker.internal:host-gateway",
"--env-file=/absolute/path/to/.env",
"mimersql/mimer-mcp:latest"
]
}
},
"inputs": []
}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.
{
"servers": {
"mimer-mcp-server": {
"command": "docker",
"args": [
"compose",
"run",
"--rm",
"-i",
"--no-TTY",
"mimer-mcp-server"
]
}
},
"inputs": []
}
{
"servers": {
"mimer-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"mimer_mcp_server"
],
"env": {
"DOTENV_PATH": "/absolute/path/to/.env"
}
}
}
}- 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)
- 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
# macOS / Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# or via Homebrew
brew install uvVerify installation:
uv --version# Linux (Ubuntu/Debian)
sudo apt install nodejs npm
# macOS (via Homebrew)
brew install nodeVerify installation:
node --version
npm --version-
Clone the repository
-
Create and activate a virtual environment
uv venv
# macOS / Linux
source .venv/bin/activate
# Windows
.venv\Scripts\activate- Install dependencies from pyproject.toml
uv sync- Configure environment variables
cp .env.example .env
# Edit .env with your database credentialsThe configuration is loaded automatically via config.py.
MCP Inspector provides a web interface for testing and debugging MCP Tools (Requires Node.js: 22.7.5+):
npx @modelcontextprotocol/inspectorNote: 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
uv run fastmcp dev /absolute/path/to/server.pyTo run the Mimer SQL docker image and mimer-mcp-server using Docker compose, run:
MCP_TRANSPORT=http docker compose upor to run it as a daemon:
MCP_TRANSPORT=http docker compose up -dThis way it is possible to call the mimer-mcp-server using HTTP and port 3333.




