The Blueshift MCP Server (Beta)

Use AI assistants to work with your Blueshift account through conversation — analyze campaigns, look up customers, inspect segments, and complete supported tasks.

Beta — We’re actively expanding the capabilities of the Blueshift MCP Server. Share your feedback to help shape what’s next.

Overview

The Blueshift MCP Server connects your Blueshift account to supported AI assistants. Once set up, you can use natural language to ask about campaign performance, look up customer profiles, inspect segments, review templates, and more.

The server uses the Model Context Protocol (MCP), an open standard for connecting AI assistants to external tools and data. Because MCP is a shared standard, Blueshift's MCP server works across multiple clients. This article covers setup for Claude, Claude Code, Codex CLI, and the Codex app.

A note on data privacy

The MCP server connects through your AI assistant and may return customer data from your account. Blueshift’s own systems are not designed to retain customer data beyond what is needed to process each request. However, the AI provider you use may process and retain conversation content in accordance with its own policies. Use only AI tools approved by your organization for handling customer data.

Prerequisites

  • A Blueshift account with admin or appropriate role permissions.
  • A supported AI assistant, installed and signed in. The Blueshift MCP server currently supports Claude, Claude Code, Codex CLI, and the Codex app.

Don’t have your AI assistant installed yet? Installing and signing in to the assistant is outside the scope of this article, but each provider has a short setup guide. Some assistants also require a paid plan to connect external tools.

Supported tasks

Here are some of the things you can do once you’re connected:

  • Analyze campaign performance — see which campaigns are driving opens, clicks, and revenue over a given time range.
  • Explore customer profiles — look up a customer by email or ID and review their activity, purchases, and engagement history.
  • Inspect segments — review segment logic and verify audience counts through conversation.
  • Review email templates — inspect and preview templates with live personalization data.
  • Understand performance trends — analyze campaign data over time.
  • Discover optimization opportunities — find AI-identified opportunities to improve campaign messaging and content.
  • Review product recommendations — explore recommendation setups and preview personalized suggestions.
  • Find answers in documentation — ask product questions and get answers from the Blueshift help center.

Looking for the full list of available tools? See Blueshift MCP Server tools.

Set up the connector

Blueshift has separate MCP servers: (US) https://app.getblueshift.com/mcp and (EU) https://app.eu.getblueshift.com/mcp. Pick the setup steps for the assistant you use, and use the URL that matches your account's region. In each case you add the server, then complete a secure OAuth 2.0 sign-in with your Blueshift credentials in the browser.

The Blueshift MCP connector is currently unlisted. It does not appear in any client’s public connector directory, so you add it manually using the URL above.

Claude

  1. In Claude, open Settings, then go to Connectors or Customize, depending on your Claude version.
  2. Click Add custom connector.
  3. Enter the following details:
    • Name: Enter a label such as Blueshift US or Blueshift EU.
    • MCP Server URL (US): https://app.getblueshift.com/mcp
    • MCP Server URL (EU): https://app.eu.getblueshift.com/mcp
    • If prompted for transport type, select HTTP and not SSE.
  4. Click Connect and complete the secure OAuth 2.0 authorization flow with your Blueshift credentials.
  5. After the connection is complete, Blueshift tools will appear in your Claude conversations.

Claude Code

  1. In your terminal, register the server with a single command:

    US:

    claude mcp add --transport http blueshift-ai https://app.getblueshift.com/mcp

    EU:

    claude mcp add --transport http blueshift-eu https://app.eu.getblueshift.com/mcp
  2. Start Claude Code by running claude, then type /mcp to view your MCP servers. The Blueshift server appears with a status of needs authentication.
  3. Select the Blueshift server and press Enter to start authentication. Your browser opens to the Blueshift authorization page.
  4. Select your account and click Authorize. When you see the confirmation that authentication is complete, return to Claude Code.
  5. The server now shows as connected, and Blueshift tools are available in your Claude Code session.

If Claude Code already has a built-in Blueshift connector at the same URL, it may take priority over the one you added, and tool discovery can return no results. If that happens, remove the manually added server — claude mcp remove blueshift-ai (US) or claude mcp remove blueshift-eu (EU) — and use the built-in connector, or keep only one Blueshift entry per region to avoid the conflict.

Codex app

  1. In the Codex app, open Settings and go to MCP servers.
  2. Click Add server.
  3. Enter the following details:

    • Name: Enter a label such as Blueshift US or Blueshift EU.
    • Transport: Select Streamable HTTP (not STDIO).
    • URL (US): https://app.getblueshift.com/mcp
    • URL (EU): https://app.eu.getblueshift.com/mcp

    Leave the bearer token and headers fields empty.

  4. Click Save. The Blueshift server appears in your list with an Authenticate option.
  5. Click Authenticate, then select your account and authorize access in the browser.
  6. Once the server shows as active, return to the app and ask it to pull Blueshift data, for example: List all campaigns in Blueshift.

Codex CLI

  1. In your terminal, register the server with a single command:

    US:

    codex mcp add blueshift --url https://app.getblueshift.com/mcp

    EU:

    codex mcp add blueshift-eu --url https://app.eu.getblueshift.com/mcp
  2. Codex detects OAuth and starts the sign-in flow, printing an authorization URL. Open that URL in your browser.
  3. Select your account and authorize access. When you see the confirmation that authentication is complete, you can close the browser window.
  4. Start Codex by running codex, then ask it to pull Blueshift data, for example: List segments in Blueshift.

Permissions and limitations

Most operations are read-only by default. The large majority of available tools only read data, while a small number can create or modify resources such as campaigns, segments, and templates. Write operations are gated by your Blueshift permissions and the capabilities of the MCP client you are using.

  • In environments that support Blueshift’s approval model, write operations may require scoped approval before they proceed.
  • In environments that do not, write attempts are denied, and no changes are made.

During beta, we recommend starting with read-focused workflows unless you have explicitly enabled and validated write support for your environment. How tool permissions and approvals are surfaced depends on your AI client. Some clients, such as the Claude app, show a per-tool permissions view where you can control when each tool is used; others do not expose tool-level controls. Depending on the client and how the connector is configured, you may be asked for approval before certain tools run or before any write action.

Try it out

Once you’re connected, start a new conversation in your AI client and try prompts like these:

Start with these

  • What can you help me do in Blueshift through this connector?
  • What Blueshift tools are available through this connector?

Explore account data

  • Look up the customer profile for user@example.com and show me their recent events.
  • List all email templates tagged “Holiday 2025”.
  • Show me my top 10 campaigns by sends in the last 30 days.

Analyze performance

  • Analyze the open rate trend for my welcome email campaign.
  • What optimization opportunities are available right now?

FAQ

Which AI assistants can I use with the MCP server?

During beta, the supported setup paths are Claude, Claude Code, Codex CLI, and the Codex app. Other MCP-compatible clients may work, but they are not officially supported.

Does the MCP server support SSE (Server-Sent Events)?

No. The Blueshift MCP server uses Streamable HTTP only. When configuring your client, select HTTP or Streamable HTTP, and not SSE.

What data does the MCP server access?

It can access Blueshift data and resources available to the authenticated user, subject to account permissions.

Can the MCP server make changes to my account?

Write tools exist, but their availability depends on your permissions and the MCP client environment. See Permissions and limitations above for details.

Is my data sent to third-party AI providers?

The MCP server communicates with your AI client. Blueshift’s own systems are not designed to retain customer data beyond what is needed to process each request. The AI provider you use may process and temporarily store conversation content in accordance with its own policies. Make sure your AI tools comply with your organization’s data handling requirements.

Get help

The Blueshift MCP Server is a beta release under active development, and we value your feedback as we continue to improve the experience.

If you have questions, run into issues, or want to share feedback, contact support@blueshift.com.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.