ai.eonik/mcp MCP Server

The ai.eonik/mcp Model Context Protocol (MCP) server connects an existing assistant (Claude, Cursor, and Codex) to an eonik account. It reads brand, research, and performance facts, then drafts outputs. It “never spends,” and you approve every cut before changes are finalized.

🛠️ Key Features

Connect assistant to eonik account
Reads brand, research, and performance facts
Drafts finished content for ad workflows
Requires user approval for edits (“every cut”)

🚀 Use Cases

Drafting on-brand ads
Using assistant tools (Claude, Cursor, Codex) with eonik facts
Incorporating research and performance facts into briefs

⚡ Developer Benefits

MCP-based setup for the listed assistants
Centralized use of eonik account data (brand, research, performance facts)
User-gated drafting via approval of cuts

⚠️ Limitations

The provided description does not specify supported tools, endpoints, or technical configuration details beyond setup links
No additional fields (e.g., toolCount) are provided here

eonik

Finished, on-brand ads without the busywork.

You see what’s worth making. eonik builds the cut. You approve. Connect Claude, Cursor, or Codex to that same account: the assistant reads and drafts; it never spends. The cut itself is made on Mac.

What the assistant can do

Read your brand, notes you asked it to remember, and ads you saved

Look up competitor ads eonik already archived (what ran, how long, how it is built)

Read your own Meta performance as facts (spend, CTR, status) — never as a prediction

Break down a public ad scene by scene

Hand you receipts so you write the brief

Install

Create an API key in eonik (workspace settings).

Add this to Claude Desktop, Cursor, or Codex:

json

{
  "mcpServers": {
    "eonik": {
      "command": "npx",
      "args": ["-y", "eonik-mcp"],
      "env": {
        "EONIK_API_KEY": "eonk_live_..."
      }
    }
  }
}

Optional: EONIK_API_URL (default https://api.eonik.ai) and EONIK_BRAND_ID if you have more than one brand.

From a clone:

bash

npm install && npm run build
export EONIK_API_KEY=eonk_live_...
node build/index.js

How the assistant should work, once connected: eonik-mcp-skill (openclaw skills install @techievena/eonik).

Download for Mac

eonik.ai/download · editor free · macOS 15+ · Apple silicon

Connect an assistant

eonik.ai/mcp

Homebrew

homebrew-tap

Save ads you see

Chrome extension

Install

Configuration

Environment variables

EONIK_API_KEYrequiredsecret

An eonik API key (Settings, API keys)

EONIK_API_URL

API origin (default https://api.eonik.ai)

EONIK_BRAND_ID

The brand this connection is about. Required if you have more than one.

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "eonik-mcp@3.0.0"
      ],
      "env": {
        "EONIK_API_KEY": "<YOUR_EONIK_API_KEY>",
        "EONIK_API_URL": "<YOUR_EONIK_API_URL>",
        "EONIK_BRAND_ID": "<YOUR_EONIK_BRAND_ID>"
      }
    }
  }
}

eonik

ai.eonik/mcp MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

eonik

What the assistant can do

What it cannot do

Install

Security

Also

License

Install

Configuration

Related servers