Tools Reference

The tool surface the Intempt MCP server serves: read, single-record edit and delete categories, the default wave set, how to widen it with INTEMPT_MCP_TOOLS, and what is never served.

Overview

The server serves 131 tools under INTEMPT_MCP_TOOLS=all. A fresh install serves 67 of them. The rest open when you widen the set.

This page is the map, not the catalogue. The exact, current tool names and schemas come from the live server, so read them from your MCP client's tool list or from intempt registry list. See Listing tools live below. Hand-copying 131 names into a page is how a page goes stale, so this one groups the surface by category and domain and points you at the live list for specifics.

Every tool takes names, emails and descriptions. You never pass an internal ID. See Natural language, not IDs.

📘 Good to know

The published package is @intempt-technologies/mcp. For install and host config, see MCP Server and Host Setup. For the full ceiling, see Limits.

Tool categories

Every served tool is one of these. The split is set in the registry's write-safety class, not guessed from a tool's name.

Category	Count	What it does
Read	72	Lists and detail reads. Segments, users, accounts, events, journeys, analytics, brand assets
Single-record edit	39	Edits one existing record at a time
Delete	10	Deletes one record. No undo on the Intempt side
Content generation	7	The `generate_*` tools. Each writes one record into the active project
Session and switching	6	Sign-in and org/project selection
Enrich and billing	7	5 Intempt Enrich verbs plus 2 billing reads

The 10 deletes sit inside the 39 single-record edits by write-safety, but they carry a destructive hint so a host can prompt before running one. They cover snippets, personas, studios, characters, poses, brand designs, knowledge, meeting types, journey transformers and experience metrics.

📘 Good to know

The 72 reads are not 72 separate endpoints. 57 map one-to-one, and 15 fold several near-identical reads into one tool that takes a view argument. get_user_detail is one tool that returns an overview, an activity feed or a summary depending on the view you ask for.

The default wave and how to widen it

The surface is revealed in waves so a new host is not handed 131 tools on day one. The committed default is the set named in CURRENT_WAVES. A plain install serves these waves, plus the six session tools, which are always on.

Wave	Adds	On by default
Always on	6 session tools: `login`, `logout`, `whoami`, `list_orgs`, `list_projects`, `use_project`	Yes
`core`	4 reads: segments, users, segment members, attribute columns	Yes
`meetings`	4 reads: meetings, one meeting, summary types, meeting attributes	Yes
`read`	12 reads across accounts, events, journeys, reports, dashboards	Yes
`analytics`	17 tools: funnels, retention, insights, journey and experience detail, brand reads	Yes
`meetings_ai`	7 tools: summarize, expand, relabel, meeting and settings edits	Yes
`more_reads`	10 reads: reports with dashboards, snippets, experiences, studios, brand presets	Yes
`more_reads_2`	7 reads: event attributes, studio and pose config, readiness, recipes	Yes
`content`	The 7 `generate_` tools, plus the remaining reads. Each `generate_` writes a record	No
`write`	Every remaining single-record edit, including the 10 deletes	No

That default adds up to 67: 6 session, 4 core, 4 meetings, 12 read, 17 analytics, 7 meetings_ai, 10 more_reads, 7 more_reads_2.

To change the set, set INTEMPT_MCP_TOOLS to a comma-separated list of wave names, exact tool names, or all. The variable replaces the default list rather than adding to it, so name every wave you want. When it is unset, the server uses CURRENT_WAVES.

# everything: all 131 tools
export INTEMPT_MCP_TOOLS=all

# the default read waves plus content generation
export INTEMPT_MCP_TOOLS=core,meetings,read,analytics,content

# one wave only
export INTEMPT_MCP_TOOLS=read

# a wave plus one specific tool
export INTEMPT_MCP_TOOLS=read,analyze_funnel_overall

Verification per wave

Each wave records what it has actually been called against in production. This is not a maturity label. It is a record of what was run and checked.

Wave	Status	What that means
`core`	live	All called against production, including negative controls
`meetings`	live	All four called, including a check that the columns you ask for are the columns you get
`read`	live	All 12 called against production, the detail reads with real IDs
`analytics`	live	All 17 called against production
`meetings_ai`	live	All seven called against production on one finished meeting
`more_reads`	live	All ten called, each answer checked against a second source
`more_reads_2`	live	All seven called, each answer checked against a second source
`content`	untested	`generate_text` and `generate_email` produced output once. The other five have never been called. All seven write real records
`write`	untested	Never called against production, deliberately, since doing so mutates real data. Includes the 10 deletes, which have no undo

📘 Good to know

content and write are off by default on purpose. Both change data. Turn them on when you need them, and confirm the active project first, because a generate_* tool and every edit land in whichever project is active.

Tools by domain

The 111 registry-backed tools are derived from the Intempt API, so they track the platform instead of being maintained by hand. They span the platform's domains. Here is a representative set per domain, each name verified in the registry. Your MCP client's tool list is the full, current set.

Domain	Covers	Representative tool
`accounts`	Account overview, summary, activity, tagging, owner assignment	`get_account_detail`
`users`	User overview, summary, activity, tagging, owner assignment	`get_user_detail`
`segments`	Segment lists, counts, saved views	`get_segment_match_count`
`events`	Event reads, attributes, event metrics	`list_events`
`journeys`	Journey detail views, lifecycle actions, drafts, transformers	`get_journey_detail`
`analytics`	Funnels, retention, insights, dashboards, reports	`analyze_funnel_overall`
`experiences`	Experiment and variant reads, experience metrics	`get_experience_metrics`
`deals`	Deal reads, tags, deal analytics	`get_deals_analytics`
`meetings`	Summaries, speaker names, meeting edits, settings, public recap links	`summarize_meeting`
`blu-chat`	Knowledge base, brand kit, personas, tone, snippets	`get_brand_config`
`designer`	Brand designs, studios, characters, poses	`list_brand_designs`

Content generation sits apart from the registry, in the content wave. The seven tools are generate_email, generate_sms, generate_push_notification, generate_landing_page, generate_slack_message, generate_text and generate_image. Each routes through Blu Chat and saves the content it writes into the active project.

What the server will not serve

The ceiling is deliberate. 53 registry entries are kept off the MCP surface: the 51 rated create-or-bulk-or-destructive, plus 2 stubs with no backend.

It creates nothing. No tool creates a record. Asked to create a segment, the honest answer is "use the console."
It sends nothing. There is no send_* tool. The server can generate a message, SMS, push or Slack message as a draft record, but it cannot deliver one.
No bulk operations. Every edit acts on one record.
Destructive actions stay on the CLI. join_meeting, process_journey_draft, delete_journey_draft and draft_outreach are rated destructive, so the MCP never serves them. The intempt CLI runs them after asking.

Two names from older tool lists are registered nowhere, because the features behind them are not built: search_project and list_active_workflows.

📘 Good to know

One tool is broken upstream in the Intempt backend, so retrying does not help: get_journey_analytics. It is named in the server's own instructions so an assistant does not burn a retry loop on it. Two onboarding reads, get_onboarding_brand_persona and get_onboarding_methodology_emails, answer after about a minute and are off the default surface.

Listing tools live

The registry is the source of truth, not this page. For the exact, current names and schemas:

Ask your MCP client to list tools. What it shows is what the server will serve for your configuration.
Run intempt registry list to see every platform command grouped by domain, or intempt registry describe <tool> for one tool's arguments. See the CLI commands for the full command set.

Because the names come from the registry, a tool added to the platform later shows up in the live list on its own. This page will not enumerate it, and that is the point.

Natural language, not IDs

Every tool takes names, emails and descriptions. You do not look up internal IDs and you do not pass them. Ask for "everything about sarah@acme.com" or "the Acme Corp account" and the server resolves the name to an internal ID itself, before the detail or summary call. There is no separate lookup tool.

📘 Good to know

One exception: list_users and list_segment_users search cannot match an email address. Any search term containing @ returns nothing, so an empty result does not mean the person is absent. Both are default tools, so you will hit this on a fresh install. It is a backend bug, not a usage error. See Limits for the full list of edges.

On this page