Optimove MCP Connector

📘 Version 1.1 · July 2026. API and integration reference for the Optimove Model Context Protocol (MCP) connector. For the marketer-facing setup guide, see Optimove Academy.

Optimove MCP is a hosted, OAuth-secured Model Context Protocol server that connects an MCP-compatible AI client directly to your Optimove tenant. It exposes campaigns, promotions, triggers, journeys, segments, and platform-health signals as queryable surfaces, plus a constrained set of safe-write tools that create campaign building blocks (Target Groups, triggers, calculated attributes, actions, promotions) and draft campaigns. This page is the technical reference: transport, safety contracts, the full tool catalog, authentication, and operational limits.

MCP server endpoint

The connector is hosted at https://mcp.optimove.net/mcp.

The endpoint is hosted, HTTPS-only, and uses Streamable HTTP transport. There is nothing to install locally — clients connect to the remote server directly.

Supported clients

Optimove MCP works with any MCP-compatible client that supports remote servers with OAuth. The following clients are supported and tested:

Claude

Claude Code
Claude Web
Claude Desktop
Claude Cowork

OpenAI

ChatGPT
Codex

Developer tools

Claude Code (Terminal)
Cursor
VS Code
Kiro
GitHub Copilot CLI (by Microsoft)

Connecting from a client

Add a remote MCP server entry pointing to https://mcp.optimove.net/mcp with OAuth authentication. The exact configuration path varies by client; consult your client's documentation for its connector or MCP-server settings.

The full machine-readable tool manifest is published at the server endpoint and is surfaced automatically by the host client once connected.

Safety model

The connector is built around two contracts: read-only by default, and safe-write where the action is reversible and non-destructive.

Read-only tools

All inspection, listing, and search tools are read-only and cannot modify state. Examples: list campaigns, get promotion details, inspect a trigger, search the knowledge base.

Safe-write tools

A constrained set of tools can create assets in Optimove. Most are building blocks — Target Groups, triggers, calculated attributes, actions, and promotions — that are created in the tenant and become available to select in the campaign builder. They do not message customers or take effect on their own; they only do something once attached to a campaign that a user activates. Campaigns are created as a draft and never activated, scheduled, or sent by the connector.

These tools cannot:

Activate, schedule, or send a campaign
Send a message to any customer
Modify or delete existing campaigns, promotions, triggers, segments, journeys, attributes, or actions
Change platform settings

Assets created via the MCP appear inside Optimove exactly like ones created in the UI. Campaign activation is always a human action in Optimove — the assistant cannot do it.

Permissions

The connector inherits the permissions of the authenticated Optimove user. A user who cannot see a campaign in the Optimove UI cannot retrieve it through the MCP. Role-based access controls are enforced server-side, not at the prompt layer.

What the connector does not do

Does not read or store conversation history
Does not access user files outside explicit tool calls
Does not transfer money, vouchers, or credits
Does not generate images, video, or audio

Tool catalog

Every tool exposed by the connector is listed below, grouped by category and annotated with its safety hint. Read-only tools may run without per-call approval; safe-write tools always prompt for confirmation.

Category	What it does	Annotation
Analyst	Read-only access to Optimove analytics and KPIs. Pulls campaign performance, channel metrics, audience size, segment counts, and tenant-level dashboards.	`readOnlyHint: true`
Explorer	Read-only inspection of Optimove entities. Lists and fetches campaigns, promotions, triggers, journeys, streams, segments, and target groups. Supports filtering by status, channel, date range, and tenant.	`readOnlyHint: true`
Knowledge	Searches Optimove product documentation and returns ranked, cited results. Answers "how does X work" and "how do I configure Y" questions.	`readOnlyHint: true`
Mission Control	Read-only access to platform-health signals: service status, running jobs, recent execution errors, pipeline state.	`readOnlyHint: true`
Builder — Target Groups	Creates a target group from a natural-language description. Saved to the tenant and selectable in the campaign builder.	`destructiveHint: true`
Builder — Triggers	Creates a real-time or event trigger. Becomes available to select in a campaign; does not fire until attached to an active campaign.	`destructiveHint: true`
Builder — Calculated Attributes	Creates a calculated attribute for use in segmentation and personalisation.	`destructiveHint: true`
Builder — Actions	Creates a reusable action that can be attached to a campaign.	`destructiveHint: true`
Builder — Promotions	Creates a promotion that can be attached to a campaign.	`destructiveHint: true`
Builder — Minigames (Gamify)	Generates and previews a playable minigame from a natural-language prompt with `create_mini_game`, then publishes it to the Optimove Minigames games library with `save_mini_game`. Becomes available to attach to an Minigames campaign; nothing is published until you save. See Gamify — AI Minigame Creator (MCP-Driven Generation).	`destructiveHint: true`
Builder — Campaigns	Creates a campaign as a draft. Draft only — does not schedule, activate, or send.	`destructiveHint: true`
Builder — Streams (coming soon)	Will create a draft multi-step Stream. Not yet available in the MVP.	`destructiveHint: true`

Authentication

Optimove MCP uses OAuth 2.0 with Dynamic Client Registration. When you connect from a new client, you are redirected to the Optimove sign-in page, where you authenticate with your normal Optimove credentials and approve the requested scope.

Scopes

The connector requests read access to the entities described above, plus safe-write access for the Builder tools. No other scopes are requested. Scopes can be revoked at any time from the Optimove user profile.

Redirect URIs

The Optimove OAuth provider allowlists the redirect URIs of each supported client so that authorization completes cleanly across every surface.

Claude surfaces:

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

Developer tools (Cursor, VS Code, Kiro, GitHub Copilot CLI) register their own redirect URIs dynamically via Dynamic Client Registration; no static allowlisting is required for these clients.

Session lifetime

Authorization is per-user and per-client. Tokens are short-lived and refreshed automatically by the host client. Revoking a session in Optimove invalidates the connector immediately.

Limits and constraints

Tool responses are capped at 25,000 tokens. Large list operations are paginated.
Tool handlers complete within 5 minutes; long-running analytics queries return a job handle for polling.
Rate limits follow standard Optimove platform rate limits, scoped per user.
MVP entities: campaigns, promotions, triggers, journeys, Streams, segments, Target Groups, channels, tenant metadata, Mission Control signals, and product documentation. Other entities will be added in subsequent releases.
The MVP supports read tools across all entities. Safe-write tools are scoped to the Builder categories above.

Data handling and privacy

All data accessed through Optimove MCP is governed by the existing Optimove Data Processing Addendum (DPA) and security commitments — the same terms that already cover your Optimove tenant.

Collected:

Tool call parameters and results, retained for short-term operational logging and audit
OAuth tokens, encrypted at rest and rotated per Optimove's standard token policy
Aggregate, anonymized usage telemetry (tool name, latency, success/failure) — never tenant data

Not collected:

Conversation history or message content from the host AI client
Customer files attached to the conversation in the host client
Any data outside the explicit tool call payload

Where data is processed: All processing happens within Optimove's existing tenant infrastructure, in the same region as your Optimove tenant. No tenant data is sent to Anthropic, OpenAI, or any other third party by the Optimove MCP server.

AI training: Optimove does not train AI models on customer data. The MCP server is a stateless gateway between the host AI client and Optimove — it does not forward tenant data to any model provider.

Full privacy policy: optimove.com/privacy-policy

Example prompts for developers and integrators

"List all draft campaigns created in the last hour and return their IDs."
"Pull the JSON definition of segment lapsed_vip and explain each predicate."
"Create a trigger that fires on a deposit event with amount greater than 100, then draft a campaign that uses it."
"Create a football-themed scratch card minigame with our brand colors and give me a live preview URL."

Support

Optimove Support Portal: support.optimove.com — open a ticket to report an MCP bug or issue
Optimove Developer Hub (API and integration reference): developer.optimove.com
Optimove Academy (training and how-to): academy.optimove.com
Your assigned Customer Success Manager

Version history

Version	Date	Changes
1.1	July 2026	Expanded supported-client list: added OpenAI surfaces (ChatGPT, Codex) and developer tools (Cursor, VS Code, Kiro, GitHub Copilot CLI) alongside the Claude surfaces (Claude Code, Web, Desktop, Cowork). Added a dedicated Supported clients section and updated Redirect URIs for the new surfaces.
1.0 (MVP)	May 2026	Initial public release. Read tools across campaigns, promotions, triggers, journeys, streams, segments, target groups, channels, tenant metadata, Mission Control, and product knowledge. Safe-write tools that create target groups, triggers, calculated attributes, actions, promotions, and minigames, plus draft campaigns. Stream drafting is planned for a future release.