AI AgentPlatform
PricingSign inBook a demo

MCP Server

Run Personyze from Claude, ChatGPT or any AI assistant

Connect your Personyze account to an AI assistant with the open Model Context Protocol. Ask how campaigns are performing, find where you are losing traffic, build a campaign, pause an action, manage audiences — in plain conversation, with no exports and no code.

https://personyze.com/mcp/
ClaudeChatGPTAny MCP clientOAuth 2.1 · revocable

What it is

Your account, inside the assistant

MCP (Model Context Protocol) is the open standard AI assistants use to work with outside services — introduced by Anthropic in late 2024 and adopted across every major assistant since. Personyze runs an MCP server, so an assistant can reach your account directly rather than you copying data between tabs.

It runs on the same external API as the full-featured API, under the same permissions. Every connected assistant rides on a key belonging to your account and can see and change only what that account can.

What you can do

What Personyze + your assistant unlocks

01

Ask how campaigns are performing

Per-action results over any date range — impressions, clicks, dismissals, your configured goals and revenue totals. It declines to quote a rate on a sample too small to mean anything, rather than quoting it anyway.

02

Find where you are losing traffic

Site-wide traffic by page, landing page, referrer, search term, device, city or country — with the personalization impressions and clicks on those pages.

03

Build and change campaigns

Describe targeting in plain words and it compiles real rules, creating the campaign in staging so live traffic is untouched. Pausing a live action is confirmed first, by name, and is reversible.

04

Manage audiences and profiles

Create audiences, add or remove members, search visitor profiles by Personyze id, your own CRM id, or email, and update profile fields.

How it works

Connect it in three steps

Copy the server URLIn Personyze, open Integrations → AI Assistants (MCP) and copy the Server URL — https://personyze.com/mcp/.
Add it to your assistantIn Claude: Settings → Connectors → Add custom connector. In ChatGPT: Settings → Connectors. Paste the URL.
Approve the connectionApprove on the Personyze screen that opens. Nothing to copy and paste — the assistant receives its own credential, scoped to your account and revocable at any time.
The AI Assistants (MCP) integration drawer in Personyze showing the MCP server URL to copy into Claude or ChatGPT
The Integrations card. Copy the Server URL into your assistant. API keys are only needed for tools that cannot open a browser — a script or an IDE plugin.
Availability: the server works today as a custom connector in both Claude and ChatGPT. It has been submitted to both connector directories and listing is pending approval — once listed, connecting becomes a one-click install. Note that both assistants gate custom connectors by plan tier.

The tools

23 tools, plus the whole API

Campaigns

list_campaignsget_campaign_targetingcreate_campaign_draftupdate_campaign_draftlist_actionsget_action_contentset_action_active

Analytics

get_campaign_performanceget_traffic_analyticsget_product_stats

Audiences

list_audiencescreate_audiencedelete_audiencelist_audience_membersadd_audience_memberremove_audience_memberget_visitorssave_visitor

Help & the rest

list_placeholderscreate_placeholdersearch_docsopen_support_ticketpersonyze_api

Anything the dedicated tools do not cover falls through to personyze_api — the same REST objects available to any API client.

Safety

Guardrails that are structural

01

New work is staged

Campaigns an assistant creates are shown only to visitors arriving from a staging IP. Real traffic keeps seeing what is live, and you publish in the panel.

02

Live changes are confirmed

Pausing or resuming an action names the action, its campaign, and what visitors stop or start seeing — one action at a time, fully reversible.

03

Access is revocable

Delete the assistant's key under Integrations to disconnect. Revocation is immediate.

04

Standards-based auth

OAuth 2.1 with PKCE, dynamic client registration (RFC 7591), and discovery per RFC 9728 and RFC 8414. Scope personyze:full.