ORMCP Server enables AI LLMs and MCP clients to easily exchange object-oriented data (in JSON format) with any relational database using the MCP
Ormcp Docs MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. ORMCP Server enables AI LLMs and MCP clients to easily exchange object-oriented data (in JSON format) with any relational database using the MCP standard protocol.
The Model Context Protocol (MCP) is an open standard that provides a unified way for AI models to interact with external tools and data sources. It standardizes communication, making it easier to integrate LLMs into complex workflows without building custom API integrations for every use case.
Once Ormcp Docs is connected, these are the calls the assistant has available:
Prerequisites — The Prerequisites tool exposed by this serverThe server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 5 environment variables: GILHARI_BASE_URL, MCP_SERVER_NAME, GILHARI_TIMEOUT, LOG_LEVEL, GILHARI_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ormcp Docs's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by softwaretree; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"mcpServers": {
"ormcp-docs": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"GILHARI_BASE_URL": "your-value",
"MCP_SERVER_NAME": "your-value",
"GILHARI_TIMEOUT": "your-value",
"LOG_LEVEL": "your-value",
"GILHARI_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GILHARI_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_SERVER_NAME | Configuration value read at startup. | Optional |
| GILHARI_TIMEOUT | Configuration value read at startup. | Optional |
| LOG_LEVEL | Configuration value read at startup. | Optional |
| GILHARI_HOST | Endpoint or connection string the server talks to. | Optional |
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.