list-connectionsLABSCO SUMMARY
Reach the database the ERP is sitting on.
ODBC is often the only way into an older system, and the ProvideX configuration that actually connects to Sage 100 is written down here. Everything runs behind a readonly flag.
What it is
An MCP server that queries databases over ODBC. Connections are declared in an .ini file with a row limit, a timeout and a readonly flag, so an assistant can read a system without being able to change it.
What you get
- Any ODBC-compatible database queried through its DSN
- Several named connections configured side by side
- The DSNs available on the machine listed
- A connection tested before you rely on it
- Tables listed and a table's schema read
- Read-only safeguards that block modification
- Sage 100 Advanced through the ProvideX driver, with the company code it needs
Requirements
Python 3.10 or higher, the UV package manager, and ODBC drivers for your databases installed on the machine. Connections live in an .ini file that sets dsn, credentials, max_rows, timeout and readonly.
Setup effort
Build from source — git clone https://github.com/tylerstoltz/mcp-odbc.git
USE CASES
01
Pulling a report out of Sage 100
Query through the ProvideX DSN with the company code set on the connection.
02
Finding out what the machine can already reach
List the ODBC DSNs installed and the connections configured for the server.
03
Checking a connection before you depend on it
Test it and get a clear error now rather than a failed query later.
04
Exploring an unfamiliar schema
List the tables, then read the schema of the one you need.
05
Letting an assistant read production
The readonly flag on the connection blocks anything that would modify data.
6 tools
Listed in project docs. Your client may show a different list.
list-available-dsnstest-connectionlist-tablesget-table-schemaexecute-queryBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
Python 3.10 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/tylerstoltz/mcp-odbc.git
cd mcp-odbc
uv venv
.venv\Scripts\activate # On Mac / Linux: source .venv/bin/activate (untested)
uv pip install -e .MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"odbc": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_MCP_ODBC>",
"run",
"odbc-mcp-server",
"--config",
"<YOUR_PATH_TO_MCP_ODBC>\\config\\<YOUR_CONFIG_INI>"
]
}
}
}
