Anysphere · AI code editor

Connect Helm to Cursor.

Track the work in Helm while Cursor writes the code.

Connect Helm to Cursor over MCP and the editor that writes your code also manages the work around it. Cursor can create a Helm task as it refactors, log time against the project, and update the stakeholder account, without leaving the editor. Add the helm server to .cursor/mcp.json and authenticate with a workspace API key.

Setup docs

Setup

Connect in three steps.

Generate a key, add the config to Cursor, 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 Cursor
Paste the block on the right into .cursor/mcp.json and drop in your key.
3
Start working
Restart Cursor and ask it to read or update your Helm workspace in plain language.

.cursor/mcp.json

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

Once connected

Cursor 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.

Try it

Things to ask Cursor.

“Create a Helm task for this refactor and log time against the project.”

“Which tasks are assigned to me this sprint?”

“Mark the auth bug task done and add a comment with the fix.”

“Open a task for this TODO and link it to the Acme project.”

FAQ

Cursor and Helm.

How do I add Helm to Cursor?

Create a .cursor/mcp.json in your project (or add it in Settings → MCP), paste the helm server block, and set HELM_API_KEY to a key from Settings → API Keys. Cursor picks it up as an MCP tool.

Can each repo connect to a different Helm project?

Yes. Keep the config in each repo's .cursor/mcp.json and set HELM_DEFAULT_PROJECT_ID per project so new tasks land in the right place.

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.

Other clients