Skip to content

BI

Pigment MCP connector

Connect Pigment to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent can list your Pigment applications, blocks and views, export metrics and tables, and trigger imports and data flows, with every call logged.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Which Pigment data flows failed overnight?

Working in Pigment with Elaichi

  • List all Pigment data flows
  • List all Pigment import configurations
  • List all Pigment applications
Ask anything…
Governance / Audit log Last 24 hours
Pigment List all Pigment applications Emily Carter · ChatGPT · 9:41 AM Done
Pigment List all Pigment import configurations Emily Carter · ChatGPT · 9:41 AM Done
Pigment List all Pigment data flows Emily Carter · ChatGPT · 9:41 AM Done
Pigment Create a Pigment data flow trigger Megan Brooks · Claude · 9:38 AM Done
Pigment Create a Pigment push CSV Ryan Hayes · Cursor · 9:35 AM Done

How to connect Pigment to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Pigment MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Pigment MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Pigment MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Pigment MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Pigment MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Pigment to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

What teams do with Pigment through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Pigment is logged.

  • Finance

    Pull the forecast numbers before the review

    Ask for an export of a metric or table from a Pigment application and get the figures in the chat. No need to open the model and hunt for the right view.

  • Finance

    Kick off month-end imports and watch them land

    Trigger an import configuration in Pigment, then ask whether it finished. The agent checks the import status so actuals are in before the close meeting.

  • Data

    Push the latest plan to Looker

    Create a push to Looker or a CSV push from a Pigment data flow so downstream dashboards carry the current plan instead of last week's numbers.

  • RevOps

    Check which data flows ran overnight

    List every Pigment data flow and ask for the status of each one. Catch a failed refresh before the sales forecast call rather than after it.

  • People

    Find the headcount block in the right application

    List Pigment applications and their blocks to locate the workforce plan, then export the headcount table for the hiring review.

  • Supply chain

    Upload supplier rates and confirm the snapshot

    Create a file in Pigment with the new rate card, then list application snapshots to confirm which version of the demand plan is current.

Try asking

  • “Which Pigment data flows failed overnight?”
  • “Export the FY25 revenue forecast table from the sales planning application.”
  • “Trigger the actuals import and tell me when it finishes.”

See all 19 Pigment tools →

What connecting Pigment gets you

6 screens from Elaichi, each doing one job for your Pigment account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which Pigment data flows failed overnight?

Export the FY25 revenue forecast table from the sales planning application.

Trigger the actuals import and tell me when it finishes.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask Pigment plain questions, get live answers.

Three starter prompts pull applications, blocks and data flow status straight from Pigment.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One Pigment endpoint for Claude, ChatGPT and Cursor.

Every client signs in over OAuth, with no SDK and no shared API key.

ElaichiTools
Tool Action Description
List all Pigment data flows List List the Data Flows configured in a Pigment application. Returns: dataFlowId, name, description, application_id, steps. Required: application_id.
Create a Pigment data flow trigger Create Trigger an execution of a Data Flow in Pigment. Returns: dataFlowExecutionId. Required: dataFlowId. 400 if the Data Flow has no runnable steps; 429 if too many concurrent executions are already running.
Create a Pigment push CSV Create Push a CSV file to a Pigment import configuration. The import starts asynchronously and Returns: importId. Required: configuration_id, file.
Create a Pigment push looker Create Trigger a Looker Look import in Pigment. Pigment pulls the Look data and runs the import asynchronously. Returns: importId. Required: configuration_id.
List all Pigment import configurations List List Pigment import configurations for the given application and block. Returns: id, name. The returned id is the configurationId needed to trigger imports or push data.

Tool catalog

19 Pigment tools, with no custom code.

Data flows, imports, exports, snapshots, blocks, views and files, cataloged and ready to call.

ElaichiToolboxes
Name Source template Tools Created

Finance toolbox

Pigment · budgets and forecasts

Pigment starter 18 Mar 4, 2026

RevOps toolbox

Pigment · sales plans and quotas

— 9 Mar 2, 2026

People toolbox

Pigment · headcount and workforce plans

— 24 Feb 27, 2026

Supply chain toolbox

Pigment · demand and inventory plans

Pigment starter 6 Feb 19, 2026

Data toolbox

Pigment · data flows and imports

— 31 Jan 30, 2026

Leadership toolbox

Pigment · snapshots and summary views

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Pigment toolbox.

Finance, RevOps and Data each see the Pigment tools scoped to their work.

ElaichiConnections
Connection Scope Status Access
PI

Pigment (Group finance)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PI

Pigment (FP&A EMEA)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PI

Pigment (RevOps)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PI

Pigment (People planning)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
PI

Pigment (Supply chain)

Connected by Ryan Hayes

Personal • Active Not shared
PI

Pigment (Data team)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share a Pigment connection, never the key.

One person connects Pigment, teammates work through it and never see the API key.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Pigment Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Pigment Applications Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Pigment Applications List Toolbox

Audit log

Every Pigment call is on the record.

When, who, what happened, type and resource, in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Pigment digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch applications

    Pigment

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Pigment

    Queued

Workflows

A schedule runs your Pigment digest itself.

Data flows are fetched, grouped, drafted into a digest, approved, then posted to Pigment.

Pigment health

Refreshed 4 minutes ago · every 15 minutes · from the applications collection

Live

Applications

1,284 ↓ 12%

Blocks

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Applications created

Last 14 days

By team

Share of activity

Group finance 34%

FP&A EMEA 27%

RevOps 21%

People planning 18%

Collections and dashboards

Pigment health, computed, with no model involved.

Four metrics, 14 days of records created and a breakdown by team, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Pigment

All three can connect Pigment to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Pigment, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Pigment tools Allow or restrict single Pigment tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Pigment call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Pigment tools for your AI agents

19 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pigment, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect Pigment to Claude?

Connect Pigment in Elaichi by pasting a Pigment API key, which you create in Pigment's settings. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and Pigment is ready in your chat.

Does Pigment work with ChatGPT and Cursor as well as Claude?

Yes. A Pigment connection in Elaichi is reached through one endpoint, https://api.elaichi.ai/mcp, and that same address works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Pigment once and every client you use picks it up.

What can an AI agent actually do with my Pigment data?

An agent can list your Pigment applications, blocks, views, files and snapshots, export a metric, list or table, and show the result in the chat. It can trigger an import or a data flow, check whether it finished, upload a file, and push a data flow out as CSV or to Looker. Short, concrete asks work best, such as export the headcount table from the FY25 plan, rather than a long paragraph.

Does connecting Pigment give the AI every application in my workspace?

No. Every call to Pigment runs inside the access of the person who signed in to Elaichi and the Pigment key behind the connection, so an agent only reaches the Pigment applications and blocks that access already allows. Elaichi can narrow that further with roles and restrictions, but it can never widen it beyond what Pigment grants.

Can my team share one Pigment connection?

Yes. One person connects Pigment with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who triggered an import or exported a table, not a shared account.

Can I stop an agent from triggering or changing things in Pigment?

Yes. Pigment restrictions in Elaichi are set per action, on a role or on one person, so you can let people export tables while restricting import triggers, data flow triggers or file uploads. A restricted tool still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

What happens to a Pigment connection when someone leaves?

Offboarding someone in Elaichi ends their access to Pigment at once, across every client they used. A shared Pigment connection keeps working for everyone else on the team. If you disconnect Pigment in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

Does the Pigment MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Pigment 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, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Pigment?

Yes. Both let Claude, ChatGPT or Cursor use Pigment. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Pigment call.

How is Elaichi different from Composio for Pigment?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Pigment: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Pigment in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot