Skip to main content
The Inflection MCP connects any MCP-compatible AI client to your Inflection workspace. Use it to build audiences, emails, tokens, segments, and journeys, pull analytics, and look up contacts — all by conversation. For client setup, see the Integrate with Claude guide or Integrate with ChatGPT.

​
Specialist Agents

ask_agent starts and polls the Inflection specialist agents. It works in two modes: pass agent_type and prompt to start a run, or pass run_id to poll an existing one. The server long-polls for approximately 12 seconds. Use ask_agent for domain Q&A as well (for example, “what’s the syntax for…”). Journeys have no specialist agent. Drive them directly with create_platform_asset(asset_type='journey') and update_platform_asset for incremental edits.

​
Platform CRUD

  • list_platform_assets — list or search any asset type: journey, email, audience, segment, static_list, email_token, webhook, inbound_webhook, form, account, conversion, salesforce_opportunity (plus Salesforce campaign variants). Supports keyword, paging, and type-specific filters.
  • get_platform_asset — fetch one asset by ID. Supported types: journey, email, segment, email_token, static_list, account, webhook, inbound_webhook, form, conversion, salesforce_opportunity.
  • create_platform_asset — create: journey, email (including clone via clone_from), email_token, tag, folder, static_list.
  • update_platform_asset — patch: email, email_content, journey, email_token, business_context, tag_asset, move_asset, folder, static_list (rename). Segment edits go through ask_agent(agent_type='segment').

​
Discovery

  • get_schema — returns schema for: person, product_activity, product_events, marketing_events, event_properties, filter_types, filters_meta, operators, email_token_columns, token_functions.
  • get_platform_context — returns: business_context, email_settings, folders, tags, settings.
  • data_dictionary — browse your real data: entities (contact, account, product_user, organisation, puom), fields, distributions, and distinct values (5 query types). Call this before composing a filter whose value was described vaguely.

​
Artifacts

  • list_artifacts / get_artifacts — retrieve asset drafts produced by a run in the current thread. Supported types: DYNAMIC_LIST, EMAIL_TEMPLATE, SEGMENT_CATEGORY, JOURNEY, and others.

​
Analytics

  • get_analytics_report — aggregate and rollup metrics: campaign_stats, campaign_aggregate, journey_rollup, journey_conversions, active_sends. Delivery and engagement variants include a display block that matches the dashboard layout.
  • get_analytics_breakdown — per-entity detail (paginated): top_links, top_email_client_opens, top_email_client_clicks, recipient_engagement (8 event types), campaign_runs, form_submissions, inbound_webhook_submissions.

​
Contacts

  • get_contact_info — supports three query types: lookup (by email → composite profile), activity_log, sf_opportunities, sf_campaigns.

​
Knowledge

  • get_knowledge — access the skill tree, cross-knowledge search, and Help Center search. Also surfaces published skills such as grade-html-email.

​
Personalized Email Versions

  • set_email_version / list_email_versions / delete_email_version — manage per-contact versions on a Personalized Email Asset: set a contact’s subject, preheader, and HTML; list existing versions; or delete one. Versions are validated on arrival (known contact, unsubscribe link present, no other tokens, 500 KB cap); contacts without a version get the asset’s default email.

​
Asset Types — Read / Write Support

​
Not Available via MCP Today

The following operations are not yet available via MCP and must be performed in the Inflection dashboard:
  • Form authoring
  • Static-list member operations
  • Webhook and conversion writes
  • Account writes
  • Segment edits via direct tool (use the segment agent instead)

​
Limits and Constraints

  • Drafts, not activation — journeys and sends are activated in the app, not via MCP.
  • Segment sizing is post-save — categories populate approximately 10 minutes after creation; per-segment previews overlap.
  • No custom CSS in emails — use standard style fields only. @media and <style> blocks belong in the BEE editor.
  • One build per request — create one email or audience at a time.

​
Prompting Best Practices

Lead with your goal. Let the agent ground in your data first. Do one thing at a time. Say “save” when the result is ready to commit.

​
Report an Issue

If a tool is not behaving as expected, contact your 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.
Additional reading:
  1. Integrate with Claude
  2. Integrate with ChatGPT