---
name: zeropipeline
description: >-
  Manage a sales CRM programmatically: pipelines, deals, customers,
  activities, tasks, notes, automations, ICP profiles, outreach campaigns,
  approvals, and reports. Use when an agent needs to read or change CRM
  state rather than browse a dashboard.
license: MIT
homepage: https://zeropipeline.ainative.studio
---

# ZeroPipeline agent skill

ZeroPipeline is an API-first CRM built for agent operation. Every capability
below is backed by a real endpoint in
https://zeropipeline.ainative.studio/openapi.json (193 operations) and exposed as an MCP tool.

## Install the MCP server

The server speaks MCP over **stdio**. There is no hosted streamable-HTTP MCP
endpoint.

Node:

```bash
npx -y @ainative/zeropipeline-mcp
```

Python:

```bash
pipx run zeropipeline-mcp
```

Claude Code / Cursor / any MCP client:

```json
{
  "mcpServers": {
    "zeropipeline": {
      "command": "npx",
      "args": ["-y", "@ainative/zeropipeline-mcp"]
    }
  }
}
```

## Credentials

On first run with no credentials the server auto-provisions a free, anonymous
workspace and prints a claim URL — no signup, no API key, no credit card. The
trial workspace lives for 72 hours and can be claimed by email to become
permanent. Set `ZERODB_EMAIL` to have the claim link delivered.

To use an existing workspace instead, set `ZEROPIPELINE_API_KEY`. Keys are
minted with an explicit `agent` role — see
https://zeropipeline.ainative.studio/auth.md.

## Tools

### Pipelines and deals
- `list_pipelines`, `get_pipeline`, `create_pipeline`
- `list_deals`, `create_deal`, `update_deal`, `move_deal_stage`
- `get_deal_score` — model-scored deal health
- `get_deal_summary`, `get_pipeline_report`

### Customers
- `list_customers`, `create_customer`, `update_customer`, `search_customers`
- `bulk_create_customers`, `bulk_tag_customers`
- `check_duplicate_customer` — call before creating, to stay idempotent
- `get_tag_coverage`

### Activities, tasks, notes, comments
- `list_activities`, `log_activity`
- `list_tasks`, `create_task`, `update_task`
- `create_note`, `list_notes`, `delete_note`
- `create_comment`, `list_comments`

### Automation and approvals
- `list_automations`, `trigger_automation`
- `list_pending_approvals`, `approve_action` — human-in-the-loop gate for
  actions an agent should not take unilaterally

### Targeting and outreach
- `create_icp_profile`, `list_icp_profiles`
- `create_outreach_campaign`, `list_outreach_campaigns`, `get_campaign_stats`

### Events
- `luma_list_events`, `luma_list_guests`, `luma_import_event`

## Conventions

- List tools page with `limit` and `offset` (or `page`). Default `limit` is 25.
- Errors return `{ error_code, message, details, request_id }`. Branch on
  `error_code`; it is stable and never localized.
- Respect `X-RateLimit-Remaining` / `X-RateLimit-Reset` and back off on `429`.
- Prefer `check_duplicate_customer` and `approve_action` over retrying writes.

## Not supported

Agent-initiated payment. Billing is Stripe-backed and finished by a human in
the web app; ZeroPipeline does not implement x402, ACP, UCP, or AP2 and does
not issue machine-payable `402` challenges.
