Enterprise MCP Server

Appier's AI suite
inside your agent

The Appier MCP server securely connects Personalization Cloud and Data Cloud to your LLM, IDE, or agent platform of choice. Your team can act on customer insights and launch campaigns without leaving the tools they already use.

OAuth 2.1 · scoped access · audited controls
Model Context Protocol
Data, segments & journeys as agent tools

Connect with the AI clients you use

The Appier MCP server speaks the open Model Context Protocol, so it drops into the assistants and agent platforms your team already trusts.

Claude
OpenAI
Gemini
Cursor

Any MCP-compatible client works — these are where teams start.

Power connected workflows

AIRIS
AIQUA
Claude

Infuse your AI with Appier context

Pull live audience insights, segments, and campaign performance from AIRIS and AIQUA straight into your assistant — grounded in your own customer data, not guesses.

Stay in the flow

Ask for a churn-risk segment in Claude or spin up a journey from your IDE. The agent handles the context-switching while your team stays focused on the decision.

Scale how you work

Summarize performance across campaigns, draft copy variants, and launch multi-step journeys in bulk — turning one marketer’s prompt into a full-funnel play.

Built for the enterprise

Security & governance, by default

Connecting an AI agent to live customer data is a trust decision. The Appier MCP server is designed so your IT and security teams can say yes with confidence.

OAuth 2.1 with PKCE

Interactive clients connect through standards-based OAuth 2.1 + PKCE; Appier's own service agents present a short-lived, forwarded identity token. No API keys pasted into prompts, no long-lived secrets in client configs.

Scoped, least-privilege access

Grant agents only the products and actions they need — read insights, build segments, draft campaigns — and revoke any scope in one click.

Full audit trail

Every tool call an agent makes is logged with user, scope, and payload, so security and ops teams can review exactly what was accessed.

Data residency & isolation

Requests stay within your Appier region. Customer data is never used to train third-party models and never leaves your tenant boundary.

Get connected in minutes

Three steps to a connected agent

1

Add the server

Drop the Appier MCP endpoint into your client’s config — pick your client below for the exact snippet.

2

Sign in with Appier

A secure OAuth window confirms your identity and the products and scopes you’re granting.

3

Start prompting

Ask your agent for insights or campaigns — it now has live AIRIS and AIQUA tools available.

terminal
claude mcp add --transport http \
  appier-enterprise \
  https://mcp.enterprise.appier.net/mcp

Frequently asked questions

It’s a remote server that exposes Appier products — starting with AIRIS and AIQUA — as tools any Model Context Protocol client can call. Your AI agents get secure, governed access to live customer insights and campaign actions.

AIRIS (customer intelligence) and AIQUA (marketing automation) are available today, with BotBonnie and the agentic Campaign and Service Agents on the roadmap.

Any MCP-compatible client. Teams most commonly connect Claude, OpenAI’s ChatGPT, Google Gemini, and Cursor, but the protocol is open and vendor-neutral.

Interactive clients connect with OAuth 2.1 + PKCE, and Appier's own service agents present a short-lived, forwarded identity token — both with scoped, least-privilege permissions. There are no static API keys in client configs, every tool call is audit-logged, and access can be revoked instantly.

No. Requests stay within your Appier region and tenant boundary, and your data is never used to train third-party foundation models.

The MCP server is included with eligible AIRIS and AIQUA plans. Talk to your account team about enabling it for your workspace.

Realizing the power of AI —
now inside every agent you use

Connect AIRIS and AIQUA to your AI stack and turn prompts into full-funnel growth.