MCP Server

Helm agents on any MCP client.

Claude Code. Cursor. Windsurf. Your own. One API key, every tool.

Helm ships an open-source MCP server that exposes 61 tools across every app on the platform. Use your Helm workspace from Claude Code, Claude Desktop, Cursor, Windsurf, or any MCP-compatible client. API-key auth, stdio transport, MIT-licensed, published on npm. Works with your team or your own custom agents built on the Claude API.

Get Early AccessSee setup docs
61 tools
Across every Helm app. Tasks, CRM, invoices, more.
Open-source
MIT-licensed. Published on npm. Self-hostable.
API-key auth
Generate a key, drop it in your MCP client.
How It Works

Three steps. No new SDK to learn.

MCP is an open standard. The server is open-source. You bring your favorite client.

Step 1

Generate an API key

In Helm, go to Settings → API Keys. Generate a key scoped to your workspace. Copy it.

Step 2

Configure your MCP client

Add the Helm MCP server to your client config. Install via npm or npx. Paste the API key as an environment variable.

Step 3

Use Helm anywhere

Your MCP client now reads and writes to your Helm workspace. Claude Code, Cursor, Windsurf, Claude Desktop. Same tools, same data.

Supported Clients

Bring your favorite client.

Any stdio-capable MCP client works. No provider lock-in.

Claude Code
Anthropic's terminal-based coding agent. Your CLI gets full Helm context.
Claude Desktop
The Claude desktop app. Chat with Claude about your Helm workspace directly.
Cursor
MCP-native inside the Cursor editor. Refactor code while tracking tasks.
Windsurf
MCP-enabled agentic IDE. Helm data alongside your codebase.
Custom agents
Build your own agent on the Claude API or any framework. stdio transport works anywhere.
Any MCP client
If it speaks MCP over stdio, it speaks Helm. No provider lock-in.
Tool Catalog

47 tools. Every app.

Your MCP client can read and write to every app on the Helm platform. Full tool-level reference in the setup docs.

4 tools

Contacts

Get, search, add, and update contacts. Full CRM access for any MCP client.

4 tools

Accounts

Read and write account records. Client companies and their full context.

5 tools

Deals

List, get, create, update, and delete deals in your sales pipeline.

1 tool

Projects

List projects in the workspace. Pair with tasks for full project context.

5 tools

Tasks

List, read, create, update tasks. Add comments. Full task lifecycle.

11 tools

Documents

Create, read, update docs. Pages, folders, bulk folder moves, and bulk creation.

2 tools

Time Entries

List tracked time and create new entries. Roll hours into invoices.

2 tools

Estimates

List estimates and create new line-item quotes for clients.

4 tools

Invoices

List, read, create, and update invoices. Stripe-native billing from any client.

5 tools

Calendar

List, read, create, update, and delete calendar events. Syncs with your workspace.

4 tools

Agent Schedules

List, create, update, and delete scheduled agent runs. Automate from your terminal.

See the full tool reference
What It Looks Like

Helm follows you.

Your workspace is available wherever your agent lives.

Run your day from Claude Code

Ask your terminal agent 'What's due today?' It reads your Helm tasks, sorted by project. Create new tasks, log time, and ship updates without leaving the CLI.

Draft proposals in Claude Desktop

Claude Desktop pulls the account from CRM, the deal from Sales Pipeline, and the last three invoices. Drafts an estimate in the right voice. You review, send.

Refactor with context in Cursor

While Cursor refactors code, it also creates a Helm task, logs time against the project, and updates the stakeholder account. One editor, two systems.

Build your own agent

Your internal SRE agent, your custom compliance workflow, your homemade Slack bot. Connect to Helm via the same MCP server. No proprietary SDK to learn.

Setup

Connect your client in under five minutes.

Generate a key, install the server, paste the config. The docs walk through each supported client line-by-line.

Setup docsView on npm
FAQ

Questions about MCP.

What is MCP?

Model Context Protocol (MCP) is an open standard from Anthropic that lets AI clients connect to external tools and data sources. Think of it as a universal adapter for agents: write your integration once, and any MCP-compatible client can use it. Helm ships an MCP server so your workspace is accessible to Claude Code, Claude Desktop, Cursor, Windsurf, and any custom agent you build.

Which MCP clients are supported?

Any client that speaks MCP over stdio. Confirmed: Claude Code, Claude Desktop, Cursor, Windsurf, and custom agents built on the Claude API or any agent framework. If you can configure a client to run a local stdio server, Helm works.

Which plans include MCP access?

MCP is included on Pro, Business, and Enterprise plans. Not available on Starter. See the Pricing page for current plan limits.

How does authentication work?

You generate a workspace-scoped API key in Helm under Settings → API Keys, then pass it to your MCP client as an environment variable (HELM_API_KEY). The key grants access to every tool your plan supports. Rotate or revoke the key from the same settings page.

Is the server open-source? Can I self-host?

Yes on both. The MCP server is MIT-licensed and published on npm as @helm-ai/mcp-server. Install via npx or global npm. You can also fork it for custom deployments.

What about a remote (HTTP) transport instead of stdio?

The current MCP server is stdio-only, which works with every popular MCP client today. Remote HTTP transport for cloud-hosted agents is on the roadmap as the MCP spec matures.

Can multiple team members use MCP simultaneously?

Yes. Generate a separate API key per team member so usage is attributable and revocable per person. Every tool call is logged in your workspace audit trail.

Bring your agent to your work.

Open-source. MIT-licensed. Included on Pro and Business plans.

Get Early AccessSee pricing