Skip to main content

Set up the Pigment MCP server

The Pigment MCP server gives AI agents access to your team's planning data — querying Pigment Applications, Metrics, and planning figures. Users can only access the Applications, Metrics, and data their existing Pigment permissions allow, so MCP grants no additional access. This guide covers enabling MCP in Pigment, registering MintMCP as an OAuth client, and connecting Pigment to MintMCP.

Prerequisites​

  • A MintMCP admin account
  • A Pigment account with the Security Administrator, Workspace Administrator, or Primary Owner role
  • Pigment AI activated in your workspace

Enable MCP in Pigment​

  1. In Pigment, go to Workspace Settings > Integrations > MCP.
  2. Toggle on MCP (Model Context Protocol). Pigment generates a unique MCP endpoint URL for this workspace.
  3. Register a new MCP client, entering https://app.mintmcp.com/oauth/callback as the callback URL.
  4. Save the client registration.
  5. Copy the MCP endpoint URL — you'll need it in the next step.

Tool capabilities reference​

The Pigment MCP server runs read-only in default mode. Individual users can turn on advanced mode (read/write) in Pigment under Settings > Advanced features > Enable advanced tools on MCP server.

ModeWhat you can do
Default (read-only)Identify the workspace, list accessible Applications, list AI-enabled Metrics, inspect a metric's structure and dimensions, and query a metric's data in natural language
Advanced (read/write)Create Applications, build and edit blocks, write formulas, design views, input data, and scan Application logic with search

These tools don't grant access on their own — every call runs as the signed-in user and respects their existing Pigment permissions.

Add Pigment to MintMCP​

Pigment supports OAuth 2.1 with Dynamic Client Registration, so MintMCP registers as an OAuth client automatically — no client credentials to configure.

  1. In MintMCP, go to MCP store > Manage store.
  2. Click + Add an MCP to your registry → Connect to an MCP by URL.
  3. Enter the MCP endpoint URL you copied from Pigment.
  4. Set Connection type to Per-user credentials.
  5. Set Authorization method to OAuth.
  6. Click Create.

When users first connect, they are redirected to Pigment to authorize access with their own Pigment account.

Multiple environments​

Each Pigment environment — Workspace, Test, and Deploy — generates its own MCP endpoint URL. To give your team MCP access to additional environments, repeat the steps above for each environment's URL, adding a separate connection in MintMCP for each one.

Security considerations​

  • Users can only access the Applications, Metrics, and data their existing Pigment permissions allow — enabling MCP does not expand access.
  • Once MCP is enabled, all workspace members can connect. Verify access rights before enabling, particularly for blocks containing sensitive data.
  • Disable AI data access on individual metrics or blocks to exclude them from MCP responses.
  • Only metrics with Number, Integer, or Boolean data types are accessible through MCP.
  • Advanced mode adds a search tool that exposes block metadata — your Application logic — regardless of a user's data access rights. Users enable advanced mode themselves, so don't rely on it to keep model structure private.

Troubleshooting​

  • A metric returns no data or is missing — only metrics with Number, Integer, or Boolean data types are accessible through MCP, and any block or metric with AI data access disabled is excluded. Check the metric's data type and AI data access setting in Pigment.
  • A user sees fewer Applications or Metrics than expected — MCP respects each user's existing Pigment permissions, so they only reach what they could already access in the workspace. Adjust their Pigment role or block permissions.
  • The MCP option is missing in Workspace Settings — Pigment AI must be activated in the workspace, and managing MCP requires the Security Administrator, Workspace Administrator, or Primary Owner role.
  • Data comes from the wrong environment — each environment (Workspace, Test, Deploy) has its own endpoint URL. Confirm the connection in MintMCP points at the intended environment's URL.

Next steps​