Enki IQ

Connect Enki IQ to your AI client

Sales intelligence over MCP: ask ChatGPT, Codex, Claude, Cursor, or any compatible client about your accounts, foresights, playbooks, opportunities, contacts, and territory plans.

Preview / requires sign-in Download configuration

Canonical Streamable HTTP endpoint: https://mcp.enkiq.ai/mcp

Preview access: Connecting starts the normal OAuth sign-in and consent flow. HTTPS does not bypass authentication, tenant isolation, or OpenAI connector approval requirements.

What Enki IQ gives your client

Choose your client

Every path connects to the same Enki IQ product and the same canonical HTTPS service. Client-specific differences are only setup and approval steps.

ChatGPT / OpenAI

Use Enki IQ sales intelligence for accounts, contacts, foresights, playbooks, opportunities, and territories from ChatGPT. OpenAI may require connector review before it is available to your workspace.

Connect →
Codex

Use Enki IQ sales intelligence for accounts, contacts, foresights, playbooks, opportunities, and territories from Codex. OAuth is discovered when Codex first connects.

Connect →Download TOML ↓
Claude

Use Enki IQ sales intelligence for accounts, contacts, foresights, playbooks, opportunities, and territories from Claude, through a custom Connector or another remote MCP setup.

Connect →Download JSON ↓
Cursor

Use Enki IQ sales intelligence for accounts, contacts, foresights, playbooks, opportunities, and territories from Cursor. Cursor opens OAuth in your browser.

Connect →Download JSON ↓
Generic MCP clients

Use Enki IQ sales intelligence for accounts, contacts, foresights, playbooks, opportunities, and territories from any compatible MCP client.

Connect →Download config ↓

Remote connection details

Use this URL in a client that supports remote MCP over Streamable HTTP https://mcp.enkiq.ai/mcp

No local installation is needed. The endpoint always serves the current Enki IQ server and requires OAuth sign-in for every tenant-scoped request.

Transport
Streamable HTTP (HTTPS)
Authentication
OAuth 2.0 + Enki IQ sign-in
Protected-resource metadata
https://mcp.enkiq.ai/.well-known/oauth-protected-resource/mcp
Authorization-server metadata
https://mcp.enkiq.ai/.well-known/oauth-authorization-server

Download a secret-free configuration

These files contain only the canonical endpoint. Do not add API keys to them; OAuth metadata and consent are discovered at connection time.

Download JSON Download TOML View connector manifest →

Manifest version 1.0.0. The remote endpoint is canonical, so capability and security updates stay centralized. When signed, the manifest publishes its key ID, public-key URL, canonicalization rule, and payload hash so you can verify it before importing.

Connection instructions

  1. ChatGPT / OpenAI: open your workspace’s Apps or Connectors settings, choose to add a remote MCP app, enter https://mcp.enkiq.ai/mcp, and complete OpenAI approval plus OAuth sign-in.
  2. Codex: import the TOML file or add [mcp_servers.enkiq] with the endpoint, then approve the browser-based OAuth flow when prompted.
  3. Claude: add a custom Connector with the endpoint (or import the JSON file where supported), then sign in and authorize Enki IQ.
  4. Cursor: import the JSON file or add an enkiq entry to .cursor/mcp.json, then finish OAuth in your browser.
  5. Generic MCP: configure a Streamable HTTP server at the endpoint and let the client follow the linked OAuth discovery metadata.

Clients that only support local stdio

An optional npm/CLI wrapper can proxy a local stdio process to this HTTPS service. It is a convenience adapter, not a second Enki IQ server or a fork of the product logic. The remote endpoint above remains canonical.

Local wrapper packaging is coming soon. Until then, use a native remote MCP/Streamable HTTP client.

Available tools (19)

Read

Write