SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Pigment to Claude

Connect Claude Web, Desktop and Cowork to Pigment MCP. Review actuals versus budget for q4, export monthly revenue plan from pigment, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Pigment logoPigment
Api Key

Pigment is a business planning platform for modeling, importing, and exporting workspace data. It helps teams automate planning workflows and keep business data organized.

26 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Pigment account to Claude via Composio Connect, enabling it to review actuals versus budget for Q4, export monthly revenue plan from Pigment, update headcount assumptions across planning model, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Pigment with

ChatGPTHermesAtomic Agent

Connecting Pigment to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Pigment account

Back in Claude, ask it to connect to Pigment or give it any Pigment-related task.

For example, ask Claude to:

  • "Review actuals versus budget for Q4"
  • "Export monthly revenue plan from Pigment"
  • "Update headcount assumptions across planning model"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Pigment account is ready to use.

What is the Pigment Claude Connector, and what's possible with it?

The Pigment MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Pigment account. It provides structured and secure access to your applications, planning blocks, views, files, imports, and data flows, so your agent can inspect workspace structure, export business data, upload files, start imports, and monitor data operations on your behalf.

  • Explore your planning workspace: Have your agent list applications, blocks, views, files, import configurations, and data flows available in Pigment.
  • Export planning data: Direct your agent to export lists, metrics, tables, or views as CSV files with the required filters, scenarios, fields, and formatting options.
  • Manage file-based imports: Let the agent upload files, push CSV data into Pigment, start Looker imports, and check import progress and results.
  • Run business data flows: Instruct your agent to trigger configured data flows and check their current status and per-step results.
  • Monitor workspace snapshots: Have your agent list scheduled, active, completed, and failed snapshots for Pigment applications.

Troubleshooting

1. Why does Claude not use the Composio connector for Pigment?

The connector can show as connected, but Claude must use it in each Pigment conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Pigment again.

2. Why does Claude show an MCP server error before Pigment connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Pigment.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Pigment.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Pigment authorization link not work?

The Composio connector is one server. Your Pigment account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Pigment connection.
  • Composio creates a fresh Pigment authorization link.
  • Open that link in your browser and finish the Pigment sign-in.

4. Why do Pigment actions fail after they worked before?

The Pigment connection can expire or lose permission.

  • Ask Claude to inspect the Pigment connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Pigment account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Pigment.
  • If the action still fails with a permission error, check that the connected account has that permission in Pigment itself.

5. How do I switch to a different Pigment account?

Claude can manage the Pigment connection for you.

  • Ask Claude to disconnect or delete the current Pigment account.
  • Ask Claude to connect Pigment again.
  • Open the new Composio authorization link for Pigment.
  • Sign in with the other Pigment account in the browser.
  • After the account connects, ask Claude to retry the Pigment task.

6. Why is my Pigment connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Pigment connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Pigment tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Pigment.
TOOLS

Supported Tools

Every Pigment action and event your agent gets out of the box.

Download File

Download the raw bytes of one file from a Pigment application.

Export List

Download a Pigment List as CSV through v1 with property selection, item and property filters, and formatting options.

Export List (Legacy)

Download a List as CSV through Pigment's officially published unversioned legacy endpoint with all documented filters and formatting options.

Export Metric

Download a Pigment Metric as CSV through v1 with scenarios, deprecated dimension filters, recursive filters, and formatting options.

Export Metric (Legacy)

Download a Metric as CSV through Pigment's officially published unversioned legacy endpoint with scenarios, deprecated and recursive filters, and all documented formatting options.

Export Table

Download a Pigment Table as CSV through v1 with metrics, scenarios, filters, selected fields, and formatting options.

Export Table (Legacy)

Download a Table as CSV through Pigment's officially published unversioned legacy endpoint with metrics, scenarios, filters, selected fields, and formatting options.

Export View

Download a Pigment view as CSV through the v1 endpoint, optionally choosing comma or semicolon delimiters.

Export View (Legacy)

Download a view as CSV through Pigment's officially published unversioned legacy endpoint; prefer v1 for new workflows.

Get Data Flow Status

Get the current status and per-step results of a Pigment Data Flow execution.

Get Import Status

Get v1 status for a CSV, integration, list-copy, or metric-copy import, optionally including the detailed report.

Get Import Status (Legacy)

Get CSV import status through Pigment's officially published unversioned legacy endpoint; prefer the v1 action for new workflows.

List Applications

List Pigment applications visible to the Modeling Metadata API key owner.

List Application Snapshots

List scheduled, in-progress, completed, and failed Pigment application snapshots.

List Blocks

List visible Pigment Lists, Transaction Lists, Metrics, and Tables, optionally for one application.

List Data Flows

List the Data Flows visible in one Pigment application.

List Files

Return one cursor-controlled page of file metadata for a Pigment application, newest first.

List Import Configurations

List Pigment import configurations, optionally narrowing the results by application and block.

List Views

List Pigment view metadata, optionally narrowing the results by application and block.

Push CSV Import

Upload CSV bytes to start a Pigment v1 import and return an import ID for status checks.

Push CSV Import (Legacy)

Upload CSV bytes to start an import through Pigment's officially published unversioned legacy endpoint; prefer v1 for new workflows.

Push Looker Import

Start a Pigment v1 Looker import from a saved configuration; the official contract declares no request body.

Push Looker Import (Legacy)

Start a Looker import through Pigment's officially published unversioned legacy endpoint; the documented operation has no request body.

Trigger Data Flow

Start one Pigment Data Flow execution and return its execution ID for status checks.

Trigger Import

Trigger a configured integration import, list-to-list copy, or metric-to-metric copy and return its import ID.

Upload File

Upload one file to a Pigment application and return the created file's metadata.

FRAMEWORKS

How to build Pigment MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Pigment MCP with ChatGPT

Hermes logo

Hermes

Use Pigment MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Pigment MCP with Atomic Agent

FAQ

Frequently asked questions

With a standalone Pigment MCP server, the agents and LLMs can only access a fixed set of Pigment tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Pigment and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Pigment tools.

Yes, absolutely. You can configure which Pigment scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Pigment data and credentials are handled as safely as possible.

Start with Pigment.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Pigment tool your agent needs.Free to start.

Start building