Imagine asking Claude “how did the APAC region do last quarter?” and getting a real answer pulled live from your SQL Server - with the right row-level security applied. That is what EQQ's MCP Gateway enables.

The one-turn experience

Generate an API key under My Account → API Keys - Claude uses this to authenticate every query.
Generate an API key under My Account → API Keys - Claude uses this to authenticate every query.
You: How many open support tickets per region for the last 30 days?
Claude: I called execute_query on the EQQ server. APAC has 42, EMEA 58, NA 31, LATAM 12. Here is the chart…

Claude does not generate SQL. It calls an EQQ tool whose input schema declares exactly which parameters are valid. The SQL was written months ago by your data steward, reviewed, tested, and marked Active.

Why this beats “give the model DB access”

  • No injection. The model never writes SQL.
  • No escalation. The API key is scoped to a role.
  • Deterministic. Same prompt, same query, same numbers - because the SQL is fixed.
  • Audit trail. Every AI call is logged alongside human runs.

Connecting Claude to your EQQ instance

  1. Create an API key under My Account → API Keys.
  2. Find the MCP endpoint URL under My Account → AI Assistant Integration — it is the /mcp path on your EQQ server.
  3. Add the following to Claude Desktop's MCP config, replacing the URL and key with your values:
{
  "mcpServers": {
    "eqq": {
      "url": "http://[your-eqq-server]/mcp",
      "headers": { "X-API-Key": "YOUR_API_KEY" }
    }
  }
}
  1. Restart Claude Desktop.

Ask a question. Watch the magic.