GRID MCP Server

An MCP server for using GRID API directly from Claude for Desktop

Local serverstdio

What is the GRID MCP server?

GRID MCP server exists for a simple reason — assistants are far more useful when they can act on GRID directly instead of describing what you should do. An MCP server for using GRID API directly from Claude for Desktop.

What you get

  1. Next, set the project up using npm:

What the assistant can call

Once GRID is connected, these are the calls the assistant has available:

  • Debugging — Since MCP servers communicate over stdio, debugging can be a challenge. It's recommended to use the [MCP

Setting it up

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.

Configuration and credentials

You will need 2 environment variables: GRID_API_TOKEN, YOUR_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.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. GRID's toolset — Debugging — is a fair guide to whether it matches your workflow. It is maintained by GRID-is; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against GRID's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the grid mcp server does with a few real requests.

Available tools

ToolWhat it does
DebuggingSince MCP servers communicate over stdio, debugging can be a challenge. It's recommended to use the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), available as a package script:

How to install the GRID MCP server

{
     "mcpServers": {
       "grid": {
         "command": "node",
         "args": ["/ABSOLUTE/PATH/TO/claude-mcp/dist/index.js"],
         "env": {
           "GRID_API_TOKEN": "YOUR_API_KEY"
         }
       }
     }
   }

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
GRID_API_TOKENCredential the server authenticates with.Yes
YOUR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use GRID to Debugging.

Frequently asked questions

You need Claude for Desktop, Node.js, Git, a GRID account with an uploaded spreadsheet, and a GRID API key from the GRID app settings.