A Model Context Protocol (MCP) server enables artificial intelligence assistants to convert natural language into SQL statements.
If you already use Focus MCP Sql, the focus mcp sql mcp server is the piece that lets your assistant work with it directly. A Model Context Protocol (MCP) server enables artificial intelligence assistants to convert natural language into SQL statements.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by FocusSearch; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Focus MCP Sql's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"focus_mcp_data": {
"command": "java",
"args": [
"-jar",
"path/to/focus_mcp_sql/focus_mcp_sql.jar"
],
"autoApprove": [
"gptText2sqlStart",
"gptText2sqlChat"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.