Skip to main content
The Inflection MCP connects any MCP-compatible AI client to your Inflection workspace. Build audiences, emails, journeys, forms, tokens, segments, and scoring models, pull dashboard-accurate analytics, and look up contacts, all by conversation, grounded in your real data. This page is a reference for the tools the MCP exposes. For client setup, see Integrate with Claude or Integrate with ChatGPT.

Understand How the MCP Works

Skills first. The MCP ships with skills: short playbooks that tell your AI client how to build each asset type correctly. Your client loads the matching skill with query_skills before it builds anything, then calls the tools the skill names. Business context on the first turn. Your client calls get_platform_context once at the start of a conversation to load your industry, target customers, and brand voice, so what it builds fits your account. Specialist agents for audiences and segments. Audiences and segments are built by Inflection specialist agents through ask_agent. A run returns within about 12 seconds; longer runs return a handle your client follows with poll_operation. Drafts, not activation. The MCP creates and edits drafts. You review and activate journeys and sends in the Inflection app. Links back to the app. Asset results include a platform_url, so your client can give you a direct link to open the asset in Inflection.
Each tool also has a usage guide your client can read at skill://tools/<tool_name>. You do not need to call tools by hand. Describe what you want and your client picks the tools.

Browse the Tools

Assets

  • list_platform_assets: list or search one asset type. Keyword search is a case-insensitive substring match. Up to 200 results per page.
  • get_platform_asset: fetch one asset by ID. Journeys return as an editable flow; landing pages return in focused views (outline, a single section, search, source, versions, or preview link).
  • create_platform_asset: create an asset. Emails and journeys can be cloned with clone_from.
  • update_platform_asset: edit an asset. Send only the fields you want to change.
  • organize_platform_asset: move assets into folders, or tag and untag them.
  • preview_platform_asset: render an email, a personalization token for sample contacts, a proposed landing-page edit, or a native form. Nothing is saved.
  • validate_platform_asset: dry-run a token expression, or run the publish check on a saved landing-page version.
  • test_platform_asset: run and inspect test runs for Email Marketing Agent emails.
  • upload_to_platform: upload an image from a public https URL to your image library, add existing contacts to a static list by ID or CSV, or upload an image or PDF to the landing-page file library.
  • delete_platform_asset: delete one contact’s personalized email version. The contact falls back to the default email. No other asset type can be deleted over MCP.

Agents and Drafts

  • ask_agent: start a run of an Inflection specialist agent with agent_id and prompt. Send one request per prompt.
  • poll_operation: check on a running agent until it finishes.
  • list_artifacts / get_artifacts: retrieve the drafts a run produced in the current conversation.
Emails, tokens, journeys, and forms are built directly by your client with the matching skill. No specialist agent is needed.

Data and Context

  • get_platform_context: your business context, email settings, tags, and email building blocks and brand recipes taken from your templates.
  • get_schema: field and event names for filters and tokens: person fields, product and marketing events, event properties, filter types, operators, trigger criteria, real-time capabilities, token columns, and token functions.
  • data_dictionary: browse your real data: entities (person, account, product_user, organisation, puom), their fields, value distributions, and distinct values. Your client uses it to match a vague value such as “enterprise” to the value actually stored.
  • get_contact_info: one area of one contact’s data per call, by email or person_id. See Look Up Contacts below.

Analytics

  • get_analytics_report: totals and rollups. See Pull Analytics below.
  • get_analytics_breakdown: paginated per-item detail.

Skills and Knowledge

  • query_skills: list, read, or see the version history of the skills available to your workspace.
  • modify_skill: create, update, publish, or retire a skill for your workspace. Requires a workspace admin role. See Build and Publish Skills.
  • get_knowledge: search the Inflection Help Center and the skills catalog.

Scoring

  • query_scoring: list or read scoring models, contact signals, and the account signal catalog.
  • modify_scoring: create or update a scoring model or contact signal. Publishing, archiving, and deleting signals happen in the app.
Account scoring is available to every workspace. Contact scoring is in limited beta. Contact your Inflection Customer Success team for access.

Review Asset Support

Build Emails

  • Visual emails are composed from building blocks and brand recipes taken from the templates in your catalog. Set up the catalog first. See Set Up Your Email Template Catalog.
  • Advanced (HTML) emails store HTML you already have. They cannot be edited in the visual editor afterward.
  • Preview for real contacts: render an email for up to 50 contacts by email or person_id to check personalization.
  • Personalized email versions: set a contact’s own subject, preheader, and HTML on a personalized email. Each version must include the {{unsubscribe_url}} token, can contain no other tokens, and must be 500 KB or smaller. Contacts without a version get the default email.
  • Email Marketing Agent emails: emails written for each contact at send time from a prompt and data you choose. Build, test, compare, and publish versions with ema-builder-agent and test_platform_asset.
The Email Marketing Agent is in limited beta. Contact your Inflection Customer Success team for access.

Build Journeys

A journey build is two steps: create the journey, then write its flow with update_platform_asset on journey_flow. Your client can send the full flow or incremental edits (insert, update, remove, move, reposition, paste). Supported steps:
  • Messaging: email, internal email
  • Timing and logic: delay, branch (by filter, field value, or token), flow group
  • Lists and data: add to list, remove from list, update value, delete contact (must be the last step)
  • Other journeys: enroll in journey, move to journey
  • Integrations: webhook, Salesforce campaign sync, wait for Salesforce sync
  • Canvas: sticky note
Merge branches. Branch arms can rejoin into shared steps, so a common tail is built once instead of copied onto every arm. Trigger journeys. Set journey_type to trigger to enroll a contact the moment an event happens, for example a form submission, an inbound webhook, or being enrolled by another journey. Trigger journeys do not support branches or flow groups.
Active journeys cannot be edited over MCP. Ask your client to clone the journey, edit the copy, and activate it in the app.

Build Forms

Build, edit, pause, and resume native Inflection forms by describing the fields you need. Your client previews the form as a field table with warnings before saving, and an edit is refused if the form changed since the preview. Pausing or resuming requires your explicit confirmation. Webflow, Formstack, and custom forms are read-only.

Build Landing Pages

Draft and edit landing pages in plain language. Every change is shown as a proposed edit before it is applied, and you can place a form or image exactly where you point in the preview.
Landing pages are in limited beta. Contact your Inflection Customer Success team for access. See Landing Pages.

Look Up Contacts

get_contact_info returns one area of a contact’s data per call. Available areas: contact (profile), account, product_user, product_activity, marketing_activity, activity_log, segmentation, org, sf_opportunities, sf_campaigns, sf_connection, and scoring (for one scoring model). Activity streams are paginated.

Pull Analytics

Numbers match the Inflection dashboard. Results include a display block with the same labels and rates the dashboard uses. Date ranges. Pass a range as {gte, lte} dates. Without one, reports cover the last 7 days. Email reports need a start date and cover at most 366 days; longer ranges are shortened and flagged. Snapshots, not trends. Each call returns one window. To compare periods, run two calls. Low-volume emails. Rate rankings skip emails with fewer than 50 deliveries by default and list them separately.

Know What Is Not Available via MCP

Perform these in the Inflection app:
  • Activating journeys and sends: always a deliberate action in the app.
  • Data connections: Snowflake, Redshift, BigQuery, Databricks, Segment, and Amplitude setup and mapping.
  • User management, SSO, and OAuth client secrets.
  • Subscription Center settings.
  • Removing static list members, clearing a list, or adding members from a saved audience. Adding existing contacts by ID or CSV is available.
  • Conversion writes.
  • Deleting forms, and field mapping for Webflow, Formstack, and custom forms.
  • Inbound and outbound webhook writes.
  • Deleting assets other than a personalized email version.
  • Creating or editing contacts.
You can still ask how to do any of these. Your client searches the Help Center with get_knowledge and walks you through the steps.

Review Limits

  • Page sizes: asset lists up to 200 per page; analytics breakdowns up to 50 per page.
  • Analytics: up to 50 journeys or emails per report; date ranges up to 366 days.
  • Email previews: up to 50 contacts per preview.
  • Personalized email versions: up to 50 per call, 500 KB each.
  • Images: public https URLs only, up to 20 MB, no SVG.
  • Journey edits: up to 500 operations per batch; active journeys must be cloned to edit.
  • One build per request: ask for one audience, segment, or email at a time.
  • Segment sizing after save: new segment categories take about 10 minutes to populate.

Follow Prompting Best Practices

Lead with your goal. “Re-engage trial users who stalled after signup” works better than a list of filters. Use business terms. Your client checks your real field values before building. Do one thing at a time. Build, review, then move to the next asset. Say “save” when you are ready. Nothing is committed until you ask. Open it in the app. Use the link in the result to review the asset before you activate it.

Report an Issue

If a tool is not behaving as expected, contact your Inflection Customer Success team in Slack with a link to the conversation, your goal, and screenshots. Include which tools you rely on and what is missing.