Anthropic · Terminal coding agent
Connect Helm to Claude Code.
Run your whole business from the same terminal you ship code in.
Connect Helm to Claude Code over MCP and your terminal agent reads and writes your whole business: tasks, projects, time, invoices, CRM, calendar, and more. Add it with one command or a project .mcp.json, authenticate with a workspace API key, and Claude Code works your Helm data alongside your codebase.
Connect in three steps.
Generate a key, add the config to Claude Code, and start working your business from your agent.
- 1
Generate an API key
In Helm, go to Settings → API Keys and create a workspace-scoped key (starts with helm_sk_).
- 2
Add the config to Claude Code
Paste the block on the right into Project .mcp.json (or ~/.claude.json) and drop in your key.
- 3
Start working
Restart Claude Code and ask it to read or update your Helm workspace in plain language.
$ claude mcp add helm -- npx -y @helm-ai/mcp-server@latest{
"mcpServers": {
"helm": {
"command": "npx",
"args": ["-y", "@helm-ai/mcp-server@latest"],
"env": { "HELM_API_KEY": "helm_sk_..." }
}
}
}Claude Code works your whole business.
One API key opens 84 tools across every Helm app. Same data your team edits by hand.
Projects & tasks
List, create, update, and comment on tasks across every project.
Time tracking
Log hours against projects and roll them into invoices.
CRM
Read and write accounts, contacts, and pipeline deals.
Invoices & estimates
Draft, read, and update invoices and line-item quotes.
Documents
Create and edit docs, pages, and folders in your workspace.
Calendar & schedules
Manage events and set up recurring agent runs.
Things to ask Claude Code.
Claude Code and Helm.
How do I add Helm to Claude Code?
Run claude mcp add helm -- npx -y @helm-ai/mcp-server@latest, then set HELM_API_KEY to a key from Settings → API Keys. You can also drop the config into a project .mcp.json so the whole repo shares it.
Does it work inside a specific project?
Yes. Put the config in the project .mcp.json and Claude Code loads Helm only for that repo. Set HELM_DEFAULT_PROJECT_ID to route new tasks to the matching Helm project automatically.
Which plans include this?
The CLI and MCP server are included on every Helm plan. See the Pricing page for current plan limits.
Is it secure?
You authenticate with a workspace-scoped API key (HELM_API_KEY). It only grants the tools your plan supports, every call is logged in your audit trail, and you can rotate or revoke it anytime from Settings → API Keys.
Use a different agent?
Helm connects the same way to every stdio MCP client.
Point Claude Code at your business.
Open-source. MIT-licensed. Included on every plan.