Skip to main content

Quick Start

Connect the ECGrid MCP Server to your AI tool in four steps.

Step 1 — Get Your Credential​

The ECGrid MCP Server supports three products. You need the credential for each product you want to use:

ProductHeaderCredential
ECGrid ConnectivityX-Connectivity-API-KeyECGrid API key — your ECGrid Portal → account settings
GPA (DataSync)X-DataSync-API-KeyGPA Personal Access Token (PAT) — from your GPA administration portal
TranslationX-Translation-API-KeyTranslation API key — provided with your Translation subscription

If you use multiple products, see Adding Multiple Products after completing setup.

🔒 Your credential goes in the config only — not in your conversation with the AI. Treat it like a password.

Step 2 — Check Node.js (Claude Desktop only)​

Developers calling the MCP server directly over HTTP: skip this step. Node.js is not required for HTTP integrations.

Open a terminal and run:

node --version

You need v18 or later. If Node.js is missing or too old, install the LTS version from nodejs.org.

Node.js is required by Claude Desktop as a local bridge to remote MCP servers — not by ECGrid. This is a one-time install.

Step 3 — Add the Config Block​

Add the following to your claude_desktop_config.json (replace YOUR_API_KEY_HERE with your ECGrid API key):

{
"mcpServers": {
"ecgrid-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.ecgrid.io/mcp",
"--header",
"X-Connectivity-API-Key:YOUR_API_KEY_HERE",
"--transport",
"http-only"
]
}
}
}

Config file location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Or open it directly: Claude Desktop → hamburger menu (☰) → Settings → Developer → Edit Config.

Fully restart Claude Desktop after saving.

Step 4 — Test the Connection​

Type this prompt in your AI tool:

Test the ECGrid MCP connection

A successful response returns your ECGrid login name, auth level, network ID, and current server time.

Adding Multiple Products​

To use DataSync (GPA) or Translation alongside Connectivity, add their headers to the same config block — one "ecgrid-mcp" entry handles everything:

{
"mcpServers": {
"ecgrid-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.ecgrid.io/mcp",
"--header",
"X-Connectivity-API-Key:YOUR_CONNECTIVITY_KEY",
"--header",
"X-DataSync-API-Key:YOUR_GPA_PAT",
"--transport",
"http-only"
]
}
}
}

The MCP Server routes each credential to its product automatically.

Need More Detail?​