vsql_mcp serves the database to AI agents over the Model Context Protocol,
from a listener inside the server process. An agent can list schemas, describe
tables, and run read-only queries. Writes stay off until you turn them on, and
the query path runs through a database account you nominate, so the agent gets
exactly the access you granted that account.
Install
vsql_mcp is not bundled with the server, so build it from the repository first
and copy the resulting vsql_mcp.veb into the directory named by the veb_dir
system variable. Then install it:
What it adds
It adds one SQL function,info(), which reports what the listener is doing.
Everything else is configuration and MCP traffic.
Example
Point the listener at a database and start it:http://127.0.0.1:3100 over MCP Streamable HTTP. The
repository carries the client configuration for each agent.
A setting written with
SET PERSIST survives a restart, but
UNINSTALL EXTENSION deletes it. After an uninstall and reinstall every
setting is back at its default, and no restart brings the old value back.See also
- Serving MySQL to AI agents over MCP — connecting an agent and what it can see
- Managing extensions — how extension settings are read and written
- Preview capabilities — what the preview flag turns on and what it promises
- Available extensions — the full catalog
- villagesql/vsql-mcp — source, client setup, and the known limitations

