iiinie MCP

Connect Claude (Desktop, Code, or any MCP client) to your iiinie workspace. Ask Claude to draft and send email campaigns, manage contacts, create content and ad plans, run outreach, pull analytics, and research trends and keyword volume — all against your own iiinie account.

iiinie's MCP server is hosted at https://app.iiinie.ai/api/mcp and authenticates with your personal API key. This package is a tiny launcher that bridges your local MCP client to it — so you don't paste raw auth headers into your config.

Quick install (Claude Desktop, one click)

1. Download iiinie-mcp.mcpb from the latest release.

2. Open it (double-click), or in Claude Desktop go to Settings → Extensions → Install Extension and select the file.

3. Paste your iiinie API key when prompted. Done.

Prefer editing config yourself, or using Claude Code / another client? See below.

Related MCP server: Paid Media MCP

1. Get your API key

1. Sign in at app.iiinie.ai.

2. Go to Settings → API Keys and create a key. It starts with iin_api_.

3. Keys are per company — the key acts on whichever company (workspace) it was created in. Create one key per company you want Claude to manage.

Treat the key like a password. Anyone with it can act on that company's data.

2. Add it to your MCP client

Claude Desktop

Open Settings → Developer → Edit Config (this opens claude_desktop_config.json) and add:

{
  "mcpServers": {
    "iiinie": {
      "command": "npx",
      "args": ["-y", "github:iiinigence/iiinie-mcp"],
      "env": {
        "IIINIE_API_KEY": "iin_api_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. You should see the iiinie tools appear.

Claude Code

claude mcp add iiinie -e IIINIE_API_KEY=iin_api_your_key_here -- npx -y github:iiinigence/iiinie-mcp

Any other MCP client

Run the launcher over stdio:

IIINIE_API_KEY=iin_api_your_key_here npx -y github:iiinigence/iiinie-mcp

Once published to npm, github:iiinigence/iiinie-mcp can be replaced with @iiinigence/iiinie-mcp.

What Claude can do with it

The exact tool set is served by the hosted endpoint and grows over time — you always get the current version, no reinstall needed.

Configuration

Troubleshooting

• ENOPACKAGEJSON / weird npx errors — your MCP client is using an old Node/npx. Point command at a modern Node's npx explicitly, e.g.

  "command": "/usr/local/bin/node",
  "args": ["/usr/local/bin/npx", "-y", "github:iiinigence/iiinie-mcp"]

  Requires Node 18+.

• Tools don't appear — confirm the key is valid (Settings → API Keys), then fully quit and reopen the client.

• Wrong company's data — the key is scoped to the company it was created in. Use the key for the company you intend Claude to manage.

• Auth errors — the key may have been revoked or belongs to a different environment than IIINIE_MCP_URL.

License

MIT © iiinie LLC · iiinie.ai