Intempt Docs
Developer DocsMCP Server

Tools Reference

The 126 tools the Intempt MCP server can serve, which 10 are on by default, and how far each wave has been verified.

Tools Reference

The server can serve 126 tools. A fresh install enables 10. The rest are opened by setting INTEMPT_MCP_TOOLS, described in MCP Server.

Every tool takes names, emails and descriptions. You never pass an internal ID.

Enabled by default

Six session tools, always on regardless of configuration:

ToolWhat it does
loginStart the browser sign-in flow
logoutClear stored credentials
whoamiShow the connected account
list_orgsList organizations you can reach
list_projectsList projects in an organization
use_projectSwitch the active org and project

Plus the four core tools:

ToolWhat it does
list_segmentsList segments with their sizes
list_usersList and search users
list_segment_usersList the users matching one segment
list_attribute_columnsList available user and account attribute columns

core is the only wave verified end to end against production.

Content generation

Seven tools, in the content wave. Each one writes a real record into the active project, so check which project is active first.

ToolExample prompt
generate_email"Write a cold outreach email for enterprise SaaS buyers"
generate_sms"Flash sale SMS with 20% off code SPRING20, ends Friday"
generate_push_notification"Abandoned cart reminder for running shoes"
generate_landing_page"Landing page for our spring sale with hero, features and CTA"
generate_slack_message"Team announcement about hitting 10k active users"
generate_text"Product description for our analytics dashboard"
generate_image"Hero image for a summer sale campaign"

Everything else, by domain

The remaining 113 tools are generated from the Intempt API, so they stay in step with the platform instead of being maintained by hand. They cover 12 areas:

DomainCovers
journeysJourney detail views, lifecycle actions (start, stop, pause), drafts, transformers
blu-chatKnowledge base, brand kit, personas, tone, snippets, outreach drafting
analyticsFunnels, retention, insights, dashboards, reports
designerBrand designs, studios, characters, poses
meetingsMeeting summaries and meeting types
experiencesExperiment and variant reads, experience metrics
usersUser overview, summary, activity, tagging, owner assignment, outreach
segmentsSegment lists, counts, saved views
eventsEvent reads, attributes, event metrics
accountsAccount overview, summary, activity, tagging, owner assignment
dealsDeal reads, tags, deal analytics
recipesRecipe reads

One tool, several views

Sixteen tools take a view argument instead of existing as a dozen near-identical tools. get_user_detail is one tool that returns an overview, an activity feed or a summary depending on the view you ask for. The consolidated set:

get_account_detail      get_user_detail         get_segment_counts
get_event_metrics       get_deal_detail         get_journey_detail
get_journey_transformers get_journey_drafts     set_journey_status
get_experience_metrics  get_brand_config        analyze_insights
analyze_funnel_overall  analyze_funnel_steps    analyze_funnel_values
analyze_retention_curve

How far each wave is verified

Enable a wave knowing what it has actually been tested against. This is not a maturity label, it is a record of what has been called against production.

WaveStatusWhat that means
coreliveAll 10 called against production, including negative controls
readpartialThe five list_* tools and get_event verified. Six detail tools never called with a valid ID
analyticspartialAll five analyze_* verified, get_journey_detail verified, five brand list_* verified. get_brand_design, get_persona and the experience metrics tools unverified
contentuntestedgenerate_text and generate_email produced output once. The other five have never been called. All seven write real records
writeuntestedNever called against production, deliberately, because doing so mutates real data. Includes the 11 deletes, which have no undo

What is not here

Nothing that creates a record. No tool creates anything, and no tool acts on many records at once. Both stay in the console deliberately. There is also no send tool, so the server cannot send an email, an SMS or a message of any kind.

Two names you may see referenced do not work yet, because the features behind them are not built: search_project and list_active_workflows.

Three more are available but currently failing on the Intempt side, so retrying does not help: get_meetings_summary, list_snippets and get_journey_list_count. Last checked 2026-08-11.

Full detail in Limits.

On this page