Search Docs…

Search Docs…

Guide

Enki MCP Setup Guide

Use Enki IQ in Claude

Enki IQ exposes your sales-intelligence data — target accounts, Foresight signals, Pursuit Playbooks, MEDDPICC qualification, territory plans, and Sandler Pain Funnels — directly inside Claude. Ask Claude questions about your pipeline and it'll call Enki IQ tools to get the answer, then summarise it in plain English.

What you can do

  • “Which Tier 1 accounts have the strongest recent buy signals?” Claude pulls signals from your Foresight monitoring (financial filings, hiring patterns, leadership changes, competitive moves, etc.) and ranks accounts.

  • “Build a Pursuit Playbook for Acme Corp.” Claude pulls the latest Foresight thesis + AI research, drafts a stakeholder map, and generates engagement plays.

  • “What's the MEDDPICC status on the Globex deal and what's still missing?” Claude inspects the opportunity, walks through each MEDDPICC dimension, and flags gaps.

  • “Enrich the contact I just added at Acme.” Claude kicks off async enrichment (Apollo + BrightData + Gemini) and tells you when it completes.

  • “Summarise my Q3 territory plan.” Claude reads the plan and gives you the tier breakdown, key industries, and top execution priorities.

What's in the box (19 tools)

Read-only:

  • Accounts: search, get full account record with research / competitors / tech stack

  • Foresights: list AI-generated theses with pain lifecycle stage + confidence (sourced from financial, hiring, tech, market, leadership, competitive, regulatory, and call-intelligence signals)

  • Playbooks: get Pursuit Playbook (stakeholder map, narrative, triggers)

  • Opportunities: list with MEDDPICC scores, get individual opportunity detail

  • Research: get account research (Gemini Deep Research output), get contact research (Apollo + BrightData synthesis)

  • Territory plans: list plans, get individual plan with strategies + execution

  • Pain funnel: list Sandler entries for an opportunity

Write:

  • Accounts: create, update

  • Contacts: create, async enrich (Apollo → BrightData → Gemini synthesis pipeline, 30–60s)

  • Opportunities: create, update

  • Playbooks: regenerate from latest Foresight + research

  • Pain funnel: add entry (auto-stages surface → impact → quantified → personal)

No destructive operations are exposed via the connector.

Install in claude.ai (Connectors Directory — recommended)

Status: Pending Anthropic's review queue. We'll update this section with the directory listing link once Enki IQ is published. Use the manual install below in the meantime.

  1. Open claude.ai → Settings → Connectors.

  2. Search for “Enki IQ” and click Add.

  3. Sign in with your Enki IQ account (OAuth handshake via Clerk).

  4. Authorize the connector. You'll be redirected back to claude.ai with Enki IQ tools available.

Install in claude.ai (manual / custom connector)

  1. Settings → Connectors → Add custom connector.

  2. Paste: https://mcp.enkiq.ai/mcp

  3. Click Connect, sign in with your Enki IQ account, click Authorize.

Install in Claude Desktop (HTTP via mcp-remote)

If you prefer Claude Desktop or want to install before the directory listing is live:

  1. Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on your OS.

  2. Add an enki-iq entry under mcpServers:

{
  "mcpServers": {
    "enki-iq": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.enkiq.ai/mcp",
        "--header",
        "Authorization: Bearer ${ENKIQ_API_KEY}"
      ],
      "env": {
        "ENKIQ_API_KEY": "ak_secret_xxxxx"
      }
    }
  }
}
{
  "mcpServers": {
    "enki-iq": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.enkiq.ai/mcp",
        "--header",
        "Authorization: Bearer ${ENKIQ_API_KEY}"
      ],
      "env": {
        "ENKIQ_API_KEY": "ak_secret_xxxxx"
      }
    }
  }
}
{
  "mcpServers": {
    "enki-iq": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.enkiq.ai/mcp",
        "--header",
        "Authorization: Bearer ${ENKIQ_API_KEY}"
      ],
      "env": {
        "ENKIQ_API_KEY": "ak_secret_xxxxx"
      }
    }
  }
}

  1. Replace ak_secret_xxxxx with your Enki IQ API key (mint one in your Enki IQ Settings → API Keys, or contact your admin).

  2. Quit and reopen Claude Desktop.

  3. Start a new chat and ask Claude to use one of the tools (“Use the enkiq_list_foresights tool with limit 3”).

Install in Claude Desktop (STDIO, local node)

For users who want zero external network dependencies in the install chain:

{
  "mcpServers": {
    "enki-iq-local": {
      "command": "node",
      "args": ["/path/to/enki-mcp-server/dist/index.js"],
      "env": {
        "TRANSPORT": "stdio",
        "ENKIQ_API_KEY": "ak_secret_xxxxx",
        "ENKIQ_API_URL": "https://api.enkiq.ai/v1"
      }
    }
  }
}
{
  "mcpServers": {
    "enki-iq-local": {
      "command": "node",
      "args": ["/path/to/enki-mcp-server/dist/index.js"],
      "env": {
        "TRANSPORT": "stdio",
        "ENKIQ_API_KEY": "ak_secret_xxxxx",
        "ENKIQ_API_URL": "https://api.enkiq.ai/v1"
      }
    }
  }
}
{
  "mcpServers": {
    "enki-iq-local": {
      "command": "node",
      "args": ["/path/to/enki-mcp-server/dist/index.js"],
      "env": {
        "TRANSPORT": "stdio",
        "ENKIQ_API_KEY": "ak_secret_xxxxx",
        "ENKIQ_API_URL": "https://api.enkiq.ai/v1"
      }
    }
  }
}

Clone https://github.com/Enki-IQ/enki-mcp-server, npm install, npm run build, then point the args at the resulting dist/index.js.

Authentication & permissions

  • OAuth (claude.ai): handled by Clerk; you authorize once and tokens auto-refresh.

  • API key (Claude Desktop): a personal Clerk-issued ak_secret_* key. Treat it like a password.

  • Scopes: the connector requests a single coarse scope (mcp:read+write). You can use any tool you have permission to use inside the Enki IQ web app — the same row-level security policies apply.

  • Data isolation: every record is bound to your Clerk user ID and enforced at the database layer (PostgreSQL row-level security). Other Enki IQ users cannot see your data via the connector, even if you share an organization.

Troubleshooting

  • "Authorization with the MCP server failed" in claude.ai web: known regression on Anthropic's side (open since late March 2026 — see GitHub issue #134). Use the Claude Desktop install path until Anthropic resolves it, or wait for the directory listing.

  • Tools don't appear in Claude Desktop after install: fully quit (Cmd+Q on macOS) and reopen — the config is read at startup. Check ~/Library/Logs/Claude/mcp-server-enki-iq.log for errors.

  • "401 Missing or malformed Authorization header": your ENKIQ_API_KEY env var isn't being substituted into the --header flag. Verify it's set in the env block of claude_desktop_config.json (Claude Desktop does NOT inherit your shell's env).

  • "Invalid or unknown API key": the key was revoked or doesn't exist. Mint a new one in Enki IQ Settings → API Keys.

Privacy & security

The connector inherits Enki IQ's full security posture: SOC 2 Type II controls (in progress), Aurora PostgreSQL with KMS-managed AES-256 at rest, TLS 1.2+ in transit, Clerk-managed authentication, per-user database isolation. We do not use your data to train AI models. Full policy at https://www.enkiq.ai/legal/privacy-policy.

Support