LABSCO SUMMARY
One uvx command in place of a server per database.
Rather than registering a separate MCP server for every database and warehouse, AgentMode takes each connection as arguments to a single uvx agentmode process, with read_only set per connection. Install buttons for VS Code and a Cursor deeplink arrive pre-filled with a MySQL connection, so the setup is editing its credentials and adding the other databases alongside it.
What it is
An all-in-one MCP server that connects your coding AI to dozens of databases, data warehouses and data pipelines. Each database connection is passed as command-line arguments such as --mysql:host and --mysql:read_only, so the assistant connects once instead of once per tool.
What you get
- Databases, data warehouses and data-pipeline platforms behind one connection
- A read_only setting on each connection, alongside its host, port, username, password and database_name
- One-click configuration of VS Code or Cursor to point at it
- Several databases on one server, each passed as its own group of arguments prefixed with the database type
- One query tool per database connection, named after that connection; while read_only is on, which is the default, a query that inserts, updates, deletes, creates, drops, alters or truncates is refused before it runs
- Connectors for Airflow, Prefect, Bitbucket, Confluence and Jira, generated from each vendor's OpenAPI specification and limited to a handful of endpoints, such as DAG runs and task logs, repository file contents, wiki search and Jira issue search
- Relational engines including MySQL, PostgreSQL, MariaDB, SQL Server, Oracle, SAP HANA and CockroachDB, and warehouses including Snowflake, BigQuery, Redshift, Databricks, ClickHouse, Trino and AWS Athena
Requirements
uv, so uvx agentmode can run, plus the host, port, username, password and database name of each database you connect. Those credentials sit in the arguments of your editor's MCP configuration.
Setup effort
One command plus credentials — uvx agentmode, then supply credentials
USE CASES
01
Giving a coding assistant access to the data stores it keeps asking about
Pass a connection for each database or warehouse you want exposed, for example --mysql:host with --mysql:read_only true, and the assistant reaches all of them through the one server it already has.
02
Setting up a new engineer's editor in one step
The README's Install Server button adds agentmode to VS Code, and a Cursor deeplink does the same, so a new hire's assistant sees the same databases as everyone else's.
03
Keeping credentials out of the assistant
On the Enterprise plan, deploy AgentMode on-premise from its Docker image and connect it to your own secrets store or vault, so database credentials are not kept in each editor's MCP configuration.
04
Adding a tool that has no MCP server yet
Enterprise plans take an OpenAPI specification and turn it into an integration.
BEFORE YOU INSTALL
What to know first
Requires
uvx on PATH
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx agentmodeMCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"agentmode": {
"command": "uvx",
"args": [
"agentmode",
"--mysql:host",
"host",
"--mysql:port",
"port",
"--mysql:username",
"username",
"--mysql:password",
"password",
"--mysql:database_name",
"database_name",
"--mysql:read_only",
"true"
]
}
}
}Cursor, Windsurf
JSON
{
"mcpServers": {
"agentmode": {
"command": "uvx",
"args": [
"agentmode",
"--mysql:host",
"host",
"--mysql:port",
"port",
"--mysql:username",
"username",
"--mysql:password",
"password",
"--mysql:database_name",
"database_name",
"--mysql:read_only",
"true"
]
}
}
}