MCP server · Inflection.io

Inflection MCP

Open endpoint → Inflection.io provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Inflection.io Type: Hosted endpoint Transport: http Host: mcp.inflection.io

Endpoint

https://mcp.inflection.io

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "inflectionio": { "url": "https://mcp.inflection.io" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "inflectionio": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.inflection.io"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://mcp.inflection.io \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

ask_agent — Start or poll an Inflection specialist agent run. Modes: pass agent_type + prompt to start, or run_id to poll. agent_type is one of audience, content, segment, token. Long-polls ~12s. Also answers domain Q&A.
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 — with keyword, paging and type-specific filters.
get_platform_asset — Fetch one asset by ID (journey, email, segment, email_token, static_list, account, webhook, inbound_webhook, form, conversion, salesforce_opportunity).
create_platform_asset — Create an asset: journey, email (including clone via clone_from), email_token, tag, folder, static_list.
update_platform_asset — Patch an asset: email, email_content, journey, email_token, business_context, tag_asset, move_asset, folder, static_list rename.
get_schema — Return schema for person, product_activity, product_events, marketing_events, event_properties, filter_types, filters_meta, operators, email_token_columns, token_functions.
get_platform_context — Return business_context, email_settings, folders, tags, settings for the workspace.
data_dictionary — Browse real workspace data — entities (contact, account, product_user, organisation, puom), fields, distributions and distinct values across 5 query types.
list_artifacts — List asset drafts produced by a run in the current thread (DYNAMIC_LIST, EMAIL_TEMPLATE, SEGMENT_CATEGORY, JOURNEY and others).
get_artifacts — Retrieve the content of asset drafts produced by a run in the current thread.
get_analytics_report — Aggregate and rollup metrics — campaign_stats, campaign_aggregate, journey_rollup, journey_conversions, active_sends.
get_analytics_breakdown — Paginated per-entity detail — top_links, top_email_client_opens, top_email_client_clicks, recipient_engagement, campaign_runs, form_submissions, inbound_webhook_submissions.
get_contact_info — Contact lookup with three query types: lookup (by email, composite profile), activity_log, sf_opportunities, sf_campaigns.
get_knowledge — Access the skill tree, cross-knowledge search and Help Center search; surfaces published skills such as grade-html-email.
set_email_version — Set one contact's subject, preheader and HTML on a Personalized Email Asset. Validated on arrival (known contact, unsubscribe link present, no other tokens, 500 KB cap).
list_email_versions — List the existing per-contact versions on a Personalized Email Asset.
delete_email_version — Delete one contact's version from a Personalized Email Asset.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.