Lesson 3

How to connect Intempt to Claude with the MCP server

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

Video comingThe video is being filmed. The steps below are the whole lesson.

In this lesson

  1. 1Connect the MCP server to your agent: in Claude Code run claude mcp add intempt -- npx -y @intempt-technologies/mcp, or configure any host to run npx -y @intempt-technologies/mcp.
  2. 2Ask the agent to log in (login tool), then check whoami and use_project to set the org and project.
  3. 3Run tools/list in your MCP client and note how many tools come back.
  4. 4Set INTEMPT_MCP_TOOLS to the waves you want, for example core,meetings,read,analytics,content, restart the host and run tools/list again.
  5. 5Leave the write wave off unless you mean it: it holds the deletes, which have no undo.
Read the reference docs for this lesson

Setup checklist

The 18 steps to wire Intempt into your stack, from installing the CLI to an agent that can work in your project. Tick them off as you go; your ticks stay in this browser.

Open the setup checklist (PDF)

0 of 18 ticked

You are done when

  • intempt --version prints 0.1.2 or newer and intempt init writes intempt.yaml.
  • intempt status and intempt generate run with no credentials; a content command fails without a key and succeeds with one.
  • tools/list count is read off the screen, then changes after setting INTEMPT_MCP_TOOLS and restarting.
  • One profile shows newly filled outside fields.

Your tech stack and tools

The core stack (everything you actually need)

Highly recommended optional upgrades that level up your work

The CLI and MCP server are free and open source. Enrichment uses AI credits; an email check costs 1 credit.