Ask Claude or ChatGPT about your UGC, products and sales

What you can ask

Type questions the way you would ask a colleague. Answers come from your own Idukki account: the same numbers as your dashboard.

What it can change, only if you allow it

A change works like the same action in your dashboard. Your plan’s tagging allowance applies, and every change is logged.

Watch it work

Three walkthroughs, 34 seconds each and silent. Figures on screen are demo data.

Questions to try first

Paste these into Claude or ChatGPT once it is connected. Swap in your own product names.

Why connect it

• A Monday report in one question. New posts, top posts and add-to-carts, from your own account.
• Content for a campaign. Name a product and get the posts that show it.
• Tagging in batches. Tag a product on ten posts in one message. It asks before any change.
• The assistant your team already uses. Nobody needs to learn another screen to get a number.
• Look-only until you say otherwise. Every change is logged with the app that made it.

What it costs

Nothing extra. It is included in every paid Idukki plan, with a monthly allowance of calls. Connecting is free. Each lookup or change your assistant makes counts as one call.

Connect Claude or ChatGPT

It takes one link and a sign-in. No key to copy.

• In Claude (claude.ai) or ChatGPT, add a custom connector. Paste this link: https://api.idukki.io/mcp.
• Sign in to Idukki when asked. Check the app name and the store it will connect.
• It connects the store you have open in your Idukki dashboard. To connect another, switch to it there first.
• Click Allow. To let it tag products, tick the box for changes. It stays off unless you tick it.
• Disconnect any time in Settings, AI tools (MCP), under connected apps.

Teach your assistant: the Idukki skill

The skill is one short file. It tells your assistant where to look for each question and how to report numbers. It also makes it ask before any change.

• Claude (claude.ai): download idukki-mcp-skill.zip and upload it as a skill in Settings.
• Claude Code: save SKILL.md as ~/.claude/skills/idukki/SKILL.md.
• Any other assistant: paste the text of SKILL.md into its custom instructions.

Questions

Claude Code, Cursor or Claude Desktop: use a key

• In your Idukki dashboard, open Settings, then AI tools (MCP) under Integrations. Create a key with a name you will recognise.
• Tick write access only if the assistant should tag products and turn galleries on or off.
• Copy the key. It starts with idk_mcp_ and is shown once. Idukki keeps only a hash of it.
• Add it to your tool with the link https://api.idukki.io/mcp and the header Authorization: Bearer <your key>.

claude mcp add --transport http idukki https://api.idukki.io/mcp --header "Authorization: Bearer YOUR_IDUKKI_MCP_KEY"

{
  "mcpServers": {
    "idukki": {
      "url": "https://api.idukki.io/mcp",
      "headers": { "Authorization": "Bearer YOUR_IDUKKI_MCP_KEY" }
    }
  }
}

{
  "mcpServers": {
    "idukki": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.idukki.io/mcp", "--header", "Authorization:${IDUKKI_AUTH}"],
      "env": { "IDUKKI_AUTH": "Bearer YOUR_IDUKKI_MCP_KEY" }
    }
  }
}

mkdir -p ~/.claude/skills/idukki
curl -s https://idukki.io/downloads/idukki-mcp-skill/SKILL.md -o ~/.claude/skills/idukki/SKILL.md

Keys and access

• A key belongs to one Idukki account and can only reach that account’s data.
• New keys are look-only. Write access is a switch per key, which you can change later.
• The tab lists your keys by name, with when each was last used. A revoked key stops on the next request.
• Make one key per assistant or teammate. Revoking one leaves the others working, and the log names the key.

For developers

JSON-RPC 2.0 over HTTP (MCP Streamable HTTP), protocol version 2024-11-05, at POST /mcp. Supported methods: initialize, ping, tools/list and tools/call. Batches (an array body) work, and notifications get no reply. Authenticate with Authorization: Bearer <key> (an x-api-key header also works). A read-only key does not see the write tools in tools/list. Calling one returns error -32003. A fixable refusal, such as an id outside your account, returns isError: true.

Only tools/call counts against the monthly allowance. A plan without MCP gets error -32030 on its first call. A plan at its limit gets -32029, with the reset date in error.data.

Read tools (every connection)

Write tools (write access only)

A new tag is merged into the post’s tags and copied to its duplicates. It is synced to Shopify product metafields, and the widget cache is refreshed. Publishing a gallery refreshes its cache too. Post, product and gallery ids must belong to your account. Every write attempt is in the audit log with the key behind it, refused ones too.

curl -s https://api.idukki.io/mcp \
  -H "Authorization: Bearer YOUR_IDUKKI_MCP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Not the same as the agent feed MCP

Idukki also runs a public, read-only MCP endpoint per store at POST /agent-feed/{bguid}/mcp. It is for AI shopping agents. It needs no key and serves only rights-cleared content: list_products, search_ugc, get_product_ugc, get_reviews and get_aggregate_rating. The connector on this page is the private one, with your analytics. The public side is on Agentic commerce.