MCP & API

Programmatic access to your workspace

Helm runs a Model Context Protocol (MCP) server that exposes the same tools your agents use, so MCP clients like Claude Code and Cursor can read and write your workspace data.

API Keys

Create keys in Settings → API Keys. There are two kinds:

• Private keys (helm_sk_) - For servers and MCP. Shown once at creation, so copy it then.
• Public keys (helm_pk_) - For client-side widgets and embeds, limited to widget operations.

Keys are workspace-scoped and inherit the permissions of the person who created them. Revoke a key anytime.

Connecting an MCP Client

Point your MCP client at the Helm MCP server and authenticate with a private key. For example, in a client config:

{
  "mcpServers": {
    "helm": {
      "command": "npx",
      "args": ["-y", "@helm-ai/mcp-server@latest"],
      "env": { "HELM_API_KEY": "helm_sk_..." }
    }
  }
}

You get tools for tasks, projects, accounts, contacts, deals, invoices, documents, calendar, and more. Tools for disabled modules are hidden.

Plan Availability

API and MCP access is included on every plan, starting with Solo. See the pricing page.