Imagga MCP connector
Connect Imagga to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can tag images, sort them into categories, flag adult content, detect faces and compare them, all inside your team's own access with every call logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Imagga to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Imagga once
-
Open Connections, choose Add connection, and pick Imagga.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Imagga API key. One person generates a token in Imagga and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Imagga MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Imagga MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Imagga MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Imagga to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Imagga through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Tag a batch of campaign photos
Upload the new campaign shots and ask for descriptive tags on each one, so the image library is searchable before anyone has to type a keyword by hand.
-
E-commerce
Sort product images into catalog categories
Run new product photos through Imagga categories and get back a suggested section for each, ready to review before the listings go live.
-
Trust and Safety
Screen user uploads for adult content
Check the day's uploads for adult content and pull the text moderation results in the same pass, then list only the items that need a human look.
-
Product
Check whether two photos show the same person
Run faces detection on a pair of profile photos and ask for a similarity score, useful for verifying a re-uploaded avatar against the original.
-
Community
Find faces in event photos before publishing
Detect how many faces appear in each gallery image so the team knows which photos need consent checks before they are posted.
-
Operations
Report on Imagga usage this month
Ask how many uploads, tags and moderation checks ran this month and get a plain summary against your plan without opening the Imagga dashboard.
Try asking
- “Tag the product photos uploaded this week and group them by category”
- “Run adult content moderation on yesterday's uploads and list anything flagged”
- “Check whether these two headshots show the same person”
AI tools
Imagga tools for your AI agents
50 tools are ready to call through Elaichi's MCP endpoint the moment you connect Imagga, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Imagga gets you
6 screens from the product, each doing one job for your Imagga account.
The agent
Ask about your images in plain language.
Type a question and get tags, categories and moderation results from live Imagga records.
- uploads
- tags
- categories
- faces detections
Ask Elaichi to work across your apps.
Tag the product photos uploaded this week and group them by category
Run adult content moderation on yesterday's uploads and list anything flagged
Check whether these two headshots show the same person
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects Imagga to every client.
Claude, ChatGPT and Cursor reach Imagga through one org endpoint, no SDK, no shared key.
Copy the endpoint
Tool catalog
50 Imagga tools, ready without writing code.
Tags, categories, faces detection and moderation, covered from the catalog with no custom code.
- List all Imagga usage
- Create a Imagga upload
- Get single Imagga upload by ID
- Get single Imagga ticket by ID
Toolboxes
Each team gets its own Imagga toolbox.
Marketing tags product photos while Trust and Safety runs moderation, each in a scoped toolbox.
- Marketing
- Trust and Safety
- E-commerce
- Product
Shared connections
Teammates use Imagga without seeing the key.
One person connects the Imagga account, shares it, and nobody else ever handles a credential.
- Marketing
- Trust and Safety
- E-commerce
- Product
Audit log
Every Imagga call is logged with a name.
See who tagged which upload, when, and what moderation check ran, in one append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule tags new uploads while you sleep.
New Imagga uploads are fetched, grouped, drafted into a digest, approved, then posted back.
Imagga digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch uploads
Imagga
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Imagga
Queued
Collections and dashboards
Imagga usage and moderation numbers, refreshed on schedule.
Uploads, tags, flagged images and faces detected, computed from Imagga records with no model involved.
Imagga health
Refreshed 4 minutes ago · every 15 minutes · from the uploads collection
Uploads
1,284 ↓ 12%
Tags
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Uploads created
Last 14 days
By team
Share of activity
Marketing 34%
Trust and Safety 27%
E-commerce 21%
Product 18%
FAQ
Frequently asked questions
How do I connect Imagga to Claude?
Two steps. In Elaichi, connect Imagga by pasting your Imagga API key, which you copy from your Imagga account. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate.
Does Imagga work with ChatGPT and Cursor as well as Claude?
Yes. Once Imagga is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Imagga once and every client picks it up.
What can an AI agent actually do with my Imagga data?
With Imagga connected, an agent can upload an image, ask for tags and categories on it, run adult content and text moderation, detect faces and compare two faces for similarity, and check your usage. Short concrete asks work best, such as tagging this week's uploads or flagging anything unsafe in a folder.
Does connecting Imagga give the AI access to everything in my account?
No. Every request to Imagga runs through the key and plan your organization connected, and only for the people you have shared it with in Elaichi. Elaichi can narrow that access further, for example to tagging only, and it never widens it beyond what the Imagga account already allows.
Can I stop an agent from deleting or changing things in Imagga?
Yes. Restrictions in Elaichi apply per action, so you can allow reading tags and categories while blocking new uploads or moderation runs. A restricted Imagga action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to an Imagga connection when someone leaves?
Offboarding that person in Elaichi ends their access to Imagga at once, across Claude, ChatGPT, Cursor and every other client. A shared Imagga connection keeps working for everyone else on the team. If you disconnect Imagga in Elaichi, it disappears from every client in one step.
Does the Imagga MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Imagga is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Imagga in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.