Skip to content
Book demo Start free trial
Local stdio

Run your business from Cursor

Add Zulu to Cursor’s MCP config and the agent in the editor can look up clients, raise invoices and check stock without leaving the project.

Start free trial Get API token

Token from Settings, then API · local MCP server @getzulu/mcp

Set up

Set up in a few minutes.

Create a token, add Zulu to the agent, then ask it something real.

  1. 01

    Create a Zulu account and an API token

    Start a free trial — no credit card. Sign in to Zulu, open Settings, then API, and create a token. It begins with zulu_. You will pass it to the connector as the environment variable ZULU_API_TOKEN.

  2. 02

    Add Zulu in Cursor

    Create or edit .cursor/mcp.json in the project, or the MCP config in Cursor Settings, and add the getzulu server. Cursor starts npx -y @getzulu/mcp on your machine. Node.js 18 or newer is required. Save the file and reload MCP servers.

  3. 03

    Ask your first question

    Ask “What Zulu account am I connected to?” to confirm the connector. Then try a real job: which quotes need a follow-up, who has not paid, or what stock is running low.

The connector

Add Zulu to Cursor.

Copy the config, swap in your token, and keep the token in the environment — not in the chat.

Cursor launches the server on your machine, same as Claude Desktop. Both packages cover the full API, reads and writes, and are generated from the OpenAPI spec. Set ZULU_READONLY=1 in the same environment when an agent should look and never change data. Node.js 18 or newer is required on the machine that launches the server.

@getzulu/mcp @getzulu/cli API reference 

# .cursor/mcp.json  (project) or Cursor Settings → MCP
{
  "mcpServers": {
    "getzulu": {
      "command": "npx",
      "args": ["-y", "@getzulu/mcp"],
      "env": {
        "ZULU_API_TOKEN": "zulu_…"
      }
    }
  }
}
Try asking

Just tell your agent what you need.

Plain language, against your live Zulu data. These ask for things the API can do today.

Follow up quotes

“Which quotes are due a follow-up this week?”

Log a call, then invoice

“Log a call on Acme Pumps, then invoice 2 × PUMP-200.”

Reorder what is low

“What's running low? Draft the purchase orders.”

Load a catalogue

“Create these 20 products from my spreadsheet.”

Chase unpaid invoices

“Who hasn't paid in 30 days?”

Confirm the connection

“What Zulu account am I connected to?”

Quotes and sales orders can be read and tracked. Creating or sending them is not on the API yet. Invoices, products, purchase orders, contacts and notes can be created.

FAQ

Questions, answered.

Do I need a Zulu account?

Yes. The connector uses an API token from a Zulu account you control. Start a free trial (no credit card), sign in, and create a token under Settings, then API. The token begins with zulu_. An agent can also open the account through the public API — POST /account/signup, then POST /account/verify — and receives a key scoped to that user.

Is there a cost per call?

No. The API, the MCP server and the CLI are included in every Zulu plan. There is no per-agent fee and no per-call charge. Authenticated requests are limited to 60 per minute per key (configurable, with higher allowances on request). Over that limit the API returns HTTP 429.

Is my data safe?

Yes. Every call uses a bearer token scoped to one user. On Cursor, @getzulu/mcp runs as a local process (stdio) and reads ZULU_API_TOKEN from the environment, so the token stays on that machine — keep it out of the chat. Revoke it any time under Settings, then API. Set ZULU_READONLY=1 to expose read tools only. Read tools are marked readOnlyHint and deletes carry destructiveHint, so the client can ask before it changes or removes data.

Which modules can the agent use?

The MCP server and CLI are generated from the OpenAPI spec, so they match the API. Live today: CRM contacts (including contact people and addresses), notes, opportunities, invoices, the product catalogue, suppliers, purchase orders, job cards, website posts, stock levels and adjustments, and file uploads. Forms can be read. Quotes, sales orders and product batches can be read and tracked. Creating or sending quotes and orders is not on the API yet, and point of sale, subscriptions, scheduling and several other modules are still coming to the API. The For AI agents page and each module page mark what is live.

Where does the Cursor config live?

Project config is .cursor/mcp.json. You can also add the same mcpServers block in Cursor Settings under MCP. Use the command npx with args -y and @getzulu/mcp, and set ZULU_API_TOKEN in env. Reload MCP servers after saving.

Also works with

Use Zulu in another agent.

Same server, same token. Pick the client you already have open.

Custom connector Grok Bot Add Zulu as a custom MCP connector. It is not in the plugin marketplace. Set up Claude Code · Desktop Claude One command in Claude Code, or a config block in Claude Desktop. Set up Codex · Agents SDK OpenAI Codex and the Agents SDK, on your machine. No ChatGPT connector. Set up Stdio Any MCP client The same local server for any client that can launch a process. Set up Reference API reference Every live endpoint, plus the OpenAPI spec the MCP server is generated from. Read the docs For builders For AI agents The capability matrix: what is live, what is read-only, and what is still coming. See the matrix

Put Cursor on your Zulu data.

Free trial, no credit card. Create a token under Settings, then API, and add the connector.

Start free trial All integrations