Cursor, Windsurf & Other MCP Tools

Many MCP-compatible tools support remote MCP servers natively — no Node.js required.

Cursor

Add to ~/.cursor/mcp.json or via Settings → MCP:

{
  "mcpServers": {
    "ecgrid-mcp": {
      "url": "https://mcp.ecgrid.io/mcp",
      "headers": {
        "X-Connectivity-API-Key": "YOUR_API_KEY_HERE"
      }
    }
  }
}

To use multiple products, add each header:

{
  "mcpServers": {
    "ecgrid-mcp": {
      "url": "https://mcp.ecgrid.io/mcp",
      "headers": {
        "X-Connectivity-API-Key": "YOUR_CONNECTIVITY_KEY",
        "X-DataSync-API-Key": "YOUR_GPA_PAT"
      }
    }
  }
}

Windsurf

Add via Settings → MCP Servers → Add Server, or edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "ecgrid-mcp": {
      "serverUrl": "https://mcp.ecgrid.io/mcp",
      "headers": {
        "X-Connectivity-API-Key": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Other MCP-Compatible Tools

Use the same server URL and header for any tool that supports remote MCP servers:

Item	Value
Server URL	https://mcp.ecgrid.io/mcp
Auth header (Connectivity)	X-Connectivity-API-Key: YOUR_API_KEY_HERE
Auth header (GPA/DataSync)	X-DataSync-API-Key: YOUR_GPA_PAT
Auth header (Translation)	X-Translation-API-Key: YOUR_TRANSLATION_KEY
Transport	HTTP (SSE response)

Config formats vary by tool version — check your tool's documentation. You can also paste the ECGrid MCP Overview URL into your AI and ask: "How do I add this MCP server to [tool name]?"

Verify the Connection

After configuring, test with:

Test the ECGrid MCP connection

Expected: your ECGrid login name, auth level, network ID, and server time.