MCP Server

Prev Next

Pigment offers Model Context Protocol (MCP) solutions that Pigment users can leverage to access Pigment features securely through AI systems such as ChatGPT, Claude and Mistral.

What is MCP?

MCP is an open standard that allows AI systems to connect to external tools and data sources in a controlled, secure, and structured way.

By exposing Pigment capabilities via MCP, you enable AI systems to query data and retrieve insights directly from Pigment—all while respecting user permissions and Workspace security policies.

🎓 Pigment Academy

See also the Pigment Feature Spotlight videos on the MCP Server:

Available Pigment tools

Tool

Description

Sample Prompt

GetApplications

Get all Applications the user has access to.

Returns the list of Applications with their ID, Name and Description. Also returns the number of accessible Applications. For use when the user asks about available Applications, or you need an Application ID for other tools.

“List all my Pigment Applications.”

GetAllMetrics

List all the Metrics the user can access in an Application.

A Metric is a function that maps a cartesian product of finite sets (called Dimensions) to values (typically, textual or numeric). Returns a list of Metrics with their IDs and Names. For use when discovering available Metrics, or when you need a Metric ID for other tools.

“Show me Metrics available for analysis in the Financial Planning application.”

GetMetricDescription

Get the structure and Properties of a Metric in the Application. Returns the Name, Data Type, Description, Dimensions and Scenarios of the Metric. Dimensions are axes for analyzing data (e.g. Time, Region, Product, Employee). For use when an understanding of the structure of a Metric is required.

"Describe the Revenue Metric."

"Show me the structure of the Headcount Metric."

"What are the Dimension Items for Product in the Revenue Metric?"

QueryData

Query data from a single Metric in an Application using a natural language query. Returns raw Metric content and metadata (name, link, Dimensions and filters). One Metric per query. Perform multiple queries if you need data over multiple metrics. For use when the user asks for specific data.

“Show me Revenue.”
“Show me Revenue for EMEA and AMER regions.”

“Show me Sales for top 10 products by Year.”

How to connect to the Pigment MCP Server

Before you begin

⚠️ Important

You need the Role and access rights of Security Administrator, Workspace Administrator or Primary Owner to set up MCP.

Ensure "AI Search" is activated on key Metrics which you want MCP to read from.

1. In Pigment

  1. Request activation by submitting a Support ticket, selecting MCP Server.

  2. Once you have been notified in the ticket that MCP has been activated, go to your Workspace and select Settings from the sidebar.

  3. Select Integrations from the sidebar then the MCP tab in the main pane.

  4. Toggle on MCP (Model Context Protocol).

A unique MCP Endpoint URL is generated, which you will need to connect a third-party AI system to Pigment. If you plan to connect multiple Workspaces, each must have its own MCP Endpoint URL and connector. Test & Deploy environments also need one MCP Endpoint URL and connector each.

2. In your AI system

Use the MCP Endpoint URL to connect third-party AI systems to Pigment tools.

By default, Pigment supports:

  • ChatGPT

  • Claude

  • Claude Code

  • Cursor

  • Mistral

  • Microsoft Copilot

  • n8n

  • Dust

  • Zapier

If you want to connect another AI system to Pigment’s MCP Server, follow the instructions in Connect a custom application below.

ChatGPT

For ChatGPT’s official documentation, see here.

Create connector

  1. Go to the ChatGPT web interface.

  2. Ensure that Developer Mode is enabled under Advanced Settings.

  3. Go to Settings and select Apps.

  4. Select Create app.

  5. Name and describe your connector (e.g. “Pigment”).

  6. Paste your Pigment MCP Endpoint URL in the MCP Server URL field.

  7. Select OAuth in the Authentication field.

  8. Leave the fields OAuth Client ID and OAuth Client Secret empty, as Pigment handles OAuth automatically.

  9. Check the “I understand and want to continue” box.

  10. Select Create.

  11. Complete the authentication workflow using your Pigment credentials.

Your connector should now be created.

Publish connector

If you are a ChatGPT Admin or Owner, you can publish the connector so it becomes available to all users in your Workspace.

  1. Go to Workplace Settings and select Connectors.

  2. Select Drafts and then the Publish button.

  3. Review safety warnings.

Once published, connectors appear in the Workspace’s approved connectors list and in users’ Apps & Connectors settings in ChatGPT.

ℹ️ Note

You do not need to have Developer Mode enabled to use the ChatGPT connector. You only need it to create the connector.

If you ask your ChatGPT admin to create a connector for your Pigment Workspace and publish it to you, you'll be able to use it even though you can't use Developer Mode.

If necessary, they can choose to publish the connector only to selected users of your organization, through ChatGPT Admin Settings.

Use connector

  1. Start a new chat.

  2. Select Add files & more then More and select your custom Pigment connector.

  3. Begin your conversation. Pigment tools can now be invoked directly in chat.

Claude

For Claude’s official documentation, see here.

Create connector

  1. Go to the Claude web interface.

  2. You need Owner privileges.

  3. Go to Admin settings and select the Connectors tab.

  4. Select Add custom connector at the bottom of the section.

  5. Name your connector.

  6. Paste your Pigment MCP Server URL in the Remote MCP server URL field.

  7. Leave the optional fields OAuth Client ID and OAuth Client Secret empty. Pigment handles OAuth automatically.

  8. Select Add.

Your connector should now be created and available for all users.

Use connector

  1. Go to Personal settings and select the Connectors tab.

  2. For your Pigment connector, select Connect and go through the authentication workflow using your Pigment credentials.

  3. Start a new chat and select Search and tools to verify that your Pigment connector is active and tools are available.

  4. Begin your conversation. Pigment tools can now be invoked directly in chat.

Claude Code

For Claude Code's official documentation, see here.

In your terminal, add the Pigment MCP server using the below command. You must specify a fixed callback port using --callback-port, otherwise Claude Code assigns a random port on each connection, which does not match the whitelisted redirect URI.

claude mcp add --transport http --callback-port 4567 pigment [YOUR-MCP-SERVER-URL]

Because Claude Code uses a local callback URL for OAuth, you need to whitelist the redirect URI for your Workspace. Submit a whitelisting request to Pigment Support with:

  • Your Workspace name or ID.

  • The redirect URI (e.g. http://localhost:4567/callback in this example).

See Connect a custom application below for more information on whitelisting requests. Once the redirect URI has been whitelisted, run claude in your terminal and the authentication flow starts automatically when Pigment tools are invoked.

Cursor

ℹ️ Note

Ensure you are using the latest version of Cursor.

For Cursor’s official documentation, see here.

In Cursor, go to Settings > Cursor Settings > Tools & MCP.

Click on New MCP Server and in the mcp.json file, paste your Pigment MCP Server URL where you see [YOUR-MCP-SERVER-URL] as follows:

{
  "mcpServers": {
    "pigment": {
      "type": http,
      "url": "[YOUR-MCP-SERVER-URL]"
    }
  }
}

After adding the MCP server, go back to the Settings page and select Connect to start the authentication flow.

When successfully connected, you see the connected MCP tool with tools enabled.

Mistral

For Mistral’s official documentation, see here.

Create connector

  1. Go to the Mistral Le Chat web interface.

  2. Select Intelligence then Connectors in the menu.

  3. Select Add Connector then Custom MCP Connector.

  4. Name your connector.

  5. Paste your Pigment MCP Server URL in the Connector Server field.

  6. Select OAuth 2.1 as authentication method.

  7. Select Connect.

  8. Complete the authentication workflow using your Pigment credentials.

Your connector should now be created and available for all users of your organization.

Use connector

  1. Start a new chat, select Enable tools and select your Pigment connector.

  2. Begin your conversation. Pigment tools can now be invoked directly in chat

Microsoft Copilot

For Microsoft’s official documentation, see here.

Create connector

  1. Go to the Copilot Studio web interface.

  2. Select Agents from the menu.

  3. Select an existing Agent or create a new one.

  4. Select Tools, Add a tool and then Model Context Protocol.

  5. Name and describe your MCP Server, paste your MCP Server URL, select OAuth 2.0 and Dynamic Discovery for authentication, and click Create.

  6. Select Create a new connection. You’ll receive an error message:
    “No MCP connector found for redirect uris ["https://global.consent.azure-apim.net/redirect/…]"

  7. Submit a whitelisting request to us with your Workspace name or ID, and the full redirect URI from the error message you received. See Connect a custom application below for more information on whitelisting requests.

  8. Once our team has whitelisted your MCP tool, try connecting again, and log in with your credentials.

Your Agent should now be able to connect to Pigment’s MCP Server.

Use connector

You can create a tool once and reuse it across multiple Copilot Agents.

Miscellaneous

For other providers, follow their respective documentation:

Permissions and access rights

When a user accesses Pigment via an MCP connector, they must authenticate with their Pigment account.

All existing Pigment permissions and access rights apply:

  • Users can only access Applications, Metrics, or data they already have access to in Pigment.

  • No additional access is granted through MCP.

Connect a custom application

If you want to connect a custom application or MCP Client to the Pigment MCP Server, you need to whitelist its redirect URI. A redirect URI is the callback URL that the OAuth authentication flow uses to return control to the MCP client after a user authorizes access.

By default, we whitelist the following redirect URIs for commonly used MCP clients:

MCP Client

OAuth Redirect URI

ChatGPT

https://chatgpt.com/connector_platform_oauth_redirect

Claude

https://claude.ai/api/mcp/auth_callback

https://claude.com/api/mcp/auth_callback

Cursor

cursor://anysphere.cursor-mcp/oauth/callback

Mistral

https://callback.mistral.ai/v1/integrations_auth/oauth2_callback

n8n

https://oauth.n8n.cloud/oauth2/callback

Dust

https://dust.tt/oauth/mcp/finalize

https://eu.dust.tt/oauth/mcp/finalize

Zapier (MCP Client)

https://zapier.com/dashboard/auth/oauth/return/App222157CLIAPI/

To whitelist a custom redirect URI:

  1. Get the redirect URI. Attempt to connect it to the Pigment MCP Server. When the OAuth authentication flow fails, you should receive an error message similar to: “No MCP connector type found for redirect uris [“https://example.com/oauth/callback”]”. The redirect URI is the URL shown in the error description (in this example: https://example.com/oauth/callback).

  2. Submit a whitelisting request. Raise a support ticket with the following information:

    1. Your Workspace name or ID.

    2. The redirect URI that needs to be whitelisted.

The Product Support team will review your request and whitelist the redirect URI for your Workspace only.

⚠️ Important

Pigment MCP Server only supports OAuth authentication. Your custom application needs to support OAuth 2.0 with Dynamic Client Registration (DCR). We don't support authentication via API Keys or other authentication methods.

Troubleshooting

If you encounter issues while connecting:

  • Connection fails: verify that your MCP URL is active and the MCP Server is enabled in your Pigment Workspace.

  • Authentication errors: make sure you have the correct role and are using valid Pigment credentials.

  • Tools not visible: confirm that AI Search is enabled for the Metrics you want to query.

  • Multiple Workspaces: check that you’re using the correct MCP URL for the Workspace you’re trying to access.