Skip to main content
Claude can use Impulse through the Model Context Protocol (MCP). Once connected, Claude can upload datasets, start training sessions, inspect artifacts, deploy models, and run predictions through the Impulse tools. This guide covers both Claude Desktop (one-click extension) and Claude Code (terminal). For direct REST API calls, see the Quickstart.

Requirements

  • Claude Desktop or the Claude Code CLI.
  • An Impulse account. An API key is optional — guest mode works without one, but sign in with a key for authenticated workflows tied to your account.
Impulse connects to the hosted production gateway (https://api.impulselabs.ai) by default. You don’t need to run anything yourself.

Claude Desktop

Install Impulse as a Claude Desktop extension (.mcpb) — no terminal required.
1

Download the extension

Download impulse-mcp.mcpb from the latest release.
2

Install it

Double-click the downloaded file, or open Claude Desktop’s Settings > Extensions, and drag the file onto the page.
3

Configure (optional)

Open the Impulse extension’s Configure panel to add an API key for authenticated access. Leave it blank to use guest mode.
4

Enable it

Make sure the extension is turned on in Settings > Extensions, then start a new conversation.

Claude Code

Register Impulse as an MCP server from the terminal.
The x-api-key header is optional — omit it to use guest mode. x-impulse-client-surface is optional too; it doesn’t affect auth, it just tags usage so it’s attributed to Claude Code rather than lumped in as unknown in your impulse_usage_summary breakdown. By default this registers the server at local scope (this project only). Add -s user to make it available in every project:
Verify it’s connected:
You should see impulse listed as ✔ Connected. To check whether it picked up your API key:
--allowedTools is only needed for non-interactive (-p) runs like the check above. In a normal interactive claude session, Claude will prompt you to approve Impulse tools the first time it calls one, and you can choose “always allow.” To skip the prompt permanently, add "mcp__impulse__*" to permissions.allow in .claude/settings.json.
.claude/settings.json

First prompt

After connecting, ask Claude to use Impulse:
If you already have dataset IDs:

What Claude can do

Once connected, Claude can use Impulse MCP tools to:
  • Upload datasets.
  • List datasets and projects.
  • Start training sessions.
  • Poll session status.
  • Inspect generated artifacts.
  • Package models for inference.
  • Deploy trained models.
  • Fetch deployment feature contracts.
  • Run predictions against deployed models.

Troubleshooting

impulse_auth_status reports guest mode even though you set an API key

Check what’s actually registered:
Confirm the x-api-key header shows your raw key with no Bearer prefix — Impulse’s API key auth expects the raw key value, not an Authorization-style scheme. If it’s wrong, remove and re-add:

Claude Code doesn’t show Impulse tools

Check the server list:
If impulse is missing or not connected, re-add it with the command above, then start a new session.

The .mcpb file won’t open in Claude Desktop’s install picker

Some macOS file pickers filter by registered file type and may not recognize .mcpb. Double-click the downloaded file directly, or drag it onto Settings > Extensions, instead of using the picker’s “choose file” dialog.