Gridly MCP Server
Gridly MCP Server. The gridly mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.
npm install 2. Build the server npm run build. Notice the index.js file in the dist folder. Please copy its absolute path and paste it into Step 4 under args 3. Open Claude Desktop app > Settings > Developer > Edit Config 4. Edit claude_desktop_config.json with the following config: json { "mcpServers": { "gridly-server": { "command": "node", "args": ["path/to/dist/folder/index.js"], "env": { "GRIDLY_API_KEY": "your_api_key_here" } } } } ## Available Tools #### Project - list_projects: List grids of a database - retrieve_project: Retrieve a project #### Database -Everything the assistant can do here goes through one of these:
Project — The Project tool exposed by this serverDatabase — The Database tool exposed by this serverGrid — The Grid tool exposed by this serverView — The View tool exposed by this serverColumn — The Column tool exposed by this serverDependency — The Dependency tool exposed by this serverRecord — The Record tool exposed by this serverYou will need one environment variable: GRIDLY_API_KEY. 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.
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.
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. Gridly's toolset — Project, Database, Grid and 4 more — is a fair guide to whether it matches your workflow. It is maintained by sangcnguyen; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Project | The Project tool exposed by this server. |
| Database | The Database tool exposed by this server. |
| Grid | The Grid tool exposed by this server. |
| View | The View tool exposed by this server. |
| Column | The Column tool exposed by this server. |
| Dependency | The Dependency tool exposed by this server. |
| Record | The Record tool exposed by this server. |
{
"mcpServers": {
"gridly-server": {
"command": "npx",
"args": ["-y", "gridly-mcp-server"],
"env": {
"GRIDLY_API_KEY": "your_api_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GRIDLY_API_KEY | Credential the server authenticates with. | Yes |
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.