Connect and authenticate

Connect a compatible MCP client to the Bluestone PIM product MCP server, then sign in through Bluestone's interactive OAuth flow. Do not put a Management API key, client secret, or copied bearer token in the MCP server configuration.

The product MCP server can operate on PIM data with your permissions. If you only need published API documentation, use the Bluestone PIM docs MCP server instead.

Ask your AI assistant to help you connect

Ask your AI assistant to help you connect to the Bluestone PIM MCP server. Copy and paste the prompt below.

Help me connect to the Bluestone PIM product MCP server in Production US.

Use this setup guide:
https://docs.api-us.bluestonepim.com/docs/bluestone-pim-mcp-connect-and-authenticate

Server URL:
https://mcp-core-public-us.bluestonepim.com/mcp

Help me set up this connection in the app we are using.
If you cannot configure it directly, guide me through the steps.
Tell me when I need to complete Bluestone sign-in myself.

After connecting, confirm the available tools and organization
context with a read-only check. Do not change any PIM data.

Depending on your app, the assistant may configure the connection or guide you through manual setup. You complete sign-in and approve access yourself.

Before you connect

You need:

• A Bluestone PIM user account with access to the organization you intend to use
• An MCP client that supports remote servers over Streamable HTTP
• Client support for interactive OAuth, including browser-based authorization
• The product MCP endpoint supplied for your environment

Add the server

Choose your client below. These instructions add Production US as bluestone-pim-production-us using https and Streamable HTTP:

https://mcp-core-public-us.bluestonepim.com/mcp

During browser sign-in, verify your Bluestone user and organization, approve access, and return to the client. After tools appear, run the safe prompt under Confirm the connection. Tool discovery confirms that tools are available; verify organization context separately before using them.

Claude web and Desktop

Claude's native remote connectors are account connections, separate from local servers in claude_desktop_config.json. Anthropic lists Free, Pro, Max, Team, and Enterprise support; Free is limited to one custom connector. Team setup requires an owner/primary owner; Enterprise also permits a custom role with Manage access to Libraries.

1. On an individual account, open Customize → Connectors → + Add → Add custom connector. On Team/Enterprise, an authorized administrator first uses Organization settings → Connectors → Add → Custom → Web; members then find it in Customize → Connectors.
2. Enter name bluestone-pim-production-us and URL https://mcp-core-public-us.bluestonepim.com/mcp. Continue through detected OAuth settings, select Sign in now and Register automatically for the OAuth client, then finish with Add. Members select Connect for the administrator-added connector.
3. Complete Bluestone sign-in and return to Claude. In the chat composer, choose + → Connectors and enable bluestone-pim-production-us.
4. Run the safe confirmation prompt and check that tools are available from that connection.

For recovery, disconnect this connector in Customize → Connectors and connect again. See Troubleshooting and limitations and Claude's remote connector instructions.

Claude Code

Use a current Claude Code installation with an authenticated Claude Code account and permission to use this remote server. From the project root, run:

claude mcp add --transport http --scope project bluestone-pim-production-us https://mcp-core-public-us.bluestonepim.com/mcp

--scope project writes the shareable project-root .mcp.json. Without it, the default local scope stores a project-specific entry in ~/.claude.json; --scope user makes it available across projects. Shared configuration does not share anyone's OAuth session.

1. Start claude, review the project server approval, then open /mcp and select bluestone-pim-production-us to authenticate.
2. Complete Bluestone sign-in in the browser and return. Check /mcp or claude mcp list for Connected, then run the safe confirmation prompt in that session.
3. To sign in again, use Re-authenticate, or Clear authentication followed by authentication, in /mcp.

See Troubleshooting and limitations and Claude Code's MCP instructions.

ChatGPT web

📘

ChatGPT plan requirements

ChatGPT Free and Plus users can connect to the Bluestone PIM MCP server when their Bluestone permissions expose only read tools. If write tools are enabled on your Bluestone PIM user account, a higher ChatGPT plan that supports write tools is required.

Enable Developer mode before adding a custom MCP connection. Access can also depend on your account and workspace policy. See OpenAI’s Developer mode setup guidance for configuration steps.

1. Enable Settings → Security and login → Developer mode.
2. Open ChatGPT Plugins, select +, and create a developer-mode app named bluestone-pim-production-us with URL https://mcp-core-public-us.bluestonepim.com/mcp and OAuth authentication. Use automatic registration rather than supplying client secrets.
3. Complete Bluestone authorization when prompted; it may start when you first invoke a tool.
4. In a new chat, open + → Developer mode and select bluestone-pim-production-us. Confirm the connection's tool list appears and run the safe confirmation prompt.

For a managed workspace showing Apps instead, the Help Center documents Settings → Apps → Advanced Settings for Developer mode and Apps → Create in user/workspace settings. Business creation requires an admin/owner; Enterprise/Edu can grant developers access through RBAC. Enter the same name, URL and OAuth choice, select Scan Tools, complete sign-in, then Create. Select the draft in the chat tools menu; select or @mention it again for messages needing new access. An administrator publishes it for ordinary members to use. These interface paths differ between the two official sources.

If creation or tool selection is unavailable, check workspace approval and plan restrictions. For connection errors, see Troubleshooting and limitations.

Cursor

Use a current Cursor client with remote MCP/OAuth support and chat tools enabled. Enterprise policy may require the server URL to be allowed.

1. Create or merge this into your project's .cursor/mcp.json; use ~/.cursor/mcp.json instead for all projects:

{
  "mcpServers": {
    "bluestone-pim-production-us": {
      "url": "https://mcp-core-public-us.bluestonepim.com/mcp"
    }
  }
}

2. Open Customize in the sidebar and enable bluestone-pim-production-us. Follow Cursor's OAuth sign-in prompt in the browser and return to Cursor.
3. In Agent chat, confirm its tools appear under Available Tools. Run the safe confirmation prompt naming bluestone-pim-production-us.

If tools do not appear, check Output → MCP Logs and Troubleshooting and limitations. See Cursor's MCP configuration and controls.

VS Code

Use current VS Code with GitHub Copilot chat access and an agent session that supports MCP tools. Sign in to Copilot first; organization policy may restrict MCP servers.

1. For a new workspace connection, create or merge this portable configuration into .mcp.json at the project root:

{
  "mcpServers": {
    "bluestone-pim-production-us": {
      "type": "http",
      "url": "https://mcp-core-public-us.bluestonepim.com/mcp"
    }
  }
}

2. Open the Command Palette, run MCP: List Servers, select bluestone-pim-production-us, and enable/start it. Review workspace trust before starting. Follow the browser OAuth authorization prompt and return to VS Code.
3. Open Chat in Agent mode. Use Configure Tools to enable this connection's tools and run the safe confirmation prompt. A populated tool list confirms discovery.

VS Code also supports .vscode/mcp.json, whose top-level key is servers. The portable .mcp.json above uses mcpServers; do not mix these wrappers. For errors, use MCP: List Servers → Show Output and Troubleshooting and limitations. See VS Code setup, MCP controls, and configuration reference.

Codex

Use a current Codex desktop app or CLI with remote Streamable HTTP and OAuth support; managed policy must permit this server.

Desktop: Open Settings → MCP servers → Add server, enter bluestone-pim-production-us, choose Streamable HTTP, and enter https://mcp-core-public-us.bluestonepim.com/mcp. Save and select Restart. Ensure the server is enabled, select Authenticate, complete Bluestone sign-in, and return. In a new conversation, type /mcp to view connected servers, then run the safe confirmation prompt. OpenAI's current documentation labels this desktop surface the ChatGPT desktop app.

CLI: Run:

codex mcp add bluestone-pim-production-us --url https://mcp-core-public-us.bluestonepim.com/mcp
codex mcp login bluestone-pim-production-us

The login command starts the browser OAuth flow. Return to the CLI after authorization, start a new codex session, and use /mcp to confirm tools loaded. codex mcp list confirms configuration; it alone does not prove tools connected.

The equivalent user configuration in ~/.codex/config.toml is:

[mcp_servers.bluestone-pim-production-us]
url = "https://mcp-core-public-us.bluestonepim.com/mcp"
enabled = true

Use the CLI commands or edit TOML; you do not need both. For CLI reauthentication, run codex mcp logout bluestone-pim-production-us, then codex mcp login bluestone-pim-production-us. See Troubleshooting and limitations and OpenAI's MCP configuration and OAuth documentation.

Other compatible clients

Add a remote Streamable HTTP server named bluestone-pim-production-us with URL https://mcp-core-public-us.bluestonepim.com/mcp. Start the connection, use the client's OAuth sign-in action, complete Bluestone authorization, and enable its tools for the conversation. Use that client's documented configuration format. Confirm tool discovery and run the safe confirmation prompt before authorizing changes.

Connect Test and Production

An MCP client can connect to more than one Bluestone PIM environment. Add Test and the appropriate Production endpoint as separate connections with names that make the target unmistakable.

Repeat the setup for your selected client using each required connection name and endpoint:

Use bluestone-pim-production for Production and bluestone-pim-production-us for Production US. Keep the Test connection separate.

Authenticate each connection separately. Each connection uses the organization and permissions of the user signed in to that environment. Adding connections does not synchronize the environments or copy any data by itself.

When both connections are available, an assistant can read supported data from one environment and create or update corresponding data in the other. Follow Copy data between environments before authorizing destination writes.

How authentication works

The endpoint uses an OAuth 2.1-based authorization flow. A compatible client discovers the protected-resource and authorization-server metadata, dynamically registers when needed, and completes an authorization-code flow with PKCE S256 in the browser. The server supports refresh tokens so a client can maintain an authorized session.

The authorization server exposes one OAuth scope, mcp. It does not provide separate scopes for read/write operations or individual tool groups. Each operation is authorized using the signed-in user’s organization and Bluestone permissions.

You should not need to handle those protocol messages manually. In particular:

• Do not paste a Management API key or bearer token into the MCP configuration.
• Do not share access tokens, refresh tokens, authorization codes, browser callback URLs, or exported client credentials.
• Verify the Bluestone user and, where the flow displays it, the organization before approving access.
• Treat the connected client like an authenticated Bluestone PIM session.

Reconnect, change user, or sign out

MCP clients store and clear OAuth state differently. Use the client's MCP connection controls to disconnect, clear authentication, or sign out. Then reconnect and complete the browser flow again when you need to:

• Change the Bluestone user or organization
• Recover from an expired or revoked authorization
• Remove access from a shared or decommissioned device

Closing a chat is not necessarily the same as signing out of the MCP server. Confirm that the client has removed the stored authorization when access must be revoked locally.

Confirm the connection

After sign-in, ask the assistant for a read-only check before authorizing any change:

Show the Bluestone PIM tools available in this connection. Without changing data, report any organization context the server exposes. If it does not expose that context, stop and tell me to verify it in Bluestone PIM. Do not create, update, archive, or delete anything.

Review the result and the client's proposed tool calls. Continue with Permissions and safe operation before using write tools.