Zero MCP Server

What is Zero MCP Server?

Zero MCP Server is the official remote MCP server for Zero, an AI-native CRM for startups and scaleups, letting Claude, ChatGPT and other assistants search, create, update and manage CRM data in your Zero workspace.

Zero combines a CRM of record (companies, contacts, deals, tasks, notes, emails and meetings) with a lead database, enrichment, email and LinkedIn sequences, reporting and agents. Zero's docs describe the MCP server as the same one Zero's own agents run on, so an external assistant can work with the same records and pipelines your team sees in the app.

How to use Zero MCP Server?

You need a Zero workspace (a 14-day trial is available, no credit card required). The connection URL is:

https://api.zero.inc/mcp

It is also shown in Zero under Settings → AI & Agents → Zero MCP, together with the tools your assistant will get. Authentication is OAuth: on first connection a browser window opens, you sign in to Zero, pick a workspace and authorize. There are no API keys to manage, and the server only reaches the workspace you chose.

Claude Code

claude mcp add --transport http zero https://api.zero.inc/mcp

Run /mcp in Claude Code and authenticate the server to complete sign-in in the browser.

Claude Desktop / claude.ai

Go to Settings → Connectors → Add custom connector, name it Zero and paste https://api.zero.inc/mcp. Click Connect and sign in to Zero when prompted.

Cursor

Add the server to ~/.cursor/mcp.json (or a project .cursor/mcp.json):

{
  "mcpServers": {
    "zero": {
      "url": "https://api.zero.inc/mcp"
    }
  }
}

VS Code

Add it to .vscode/mcp.json:

{
  "servers": {
    "zero": {
      "type": "http",
      "url": "https://api.zero.inc/mcp"
    }
  }
}

Zero's docs recommend that the assistant calls get_instructions and get_workspace_metadata at the start of every conversation. They return the data model, fields, pipeline stages and custom properties of your workspace; without them the other tools work blind.

Key features of Zero MCP Server

• Full CRM access: search and filter companies, contacts, deals, tasks, notes, invoices, issues and quotes, and create or edit records.
• Activity timelines: read the full history for a company, contact or deal, including emails, events, notes, tasks, LinkedIn and Slack activity.
• Email and calendar: search synced email, read calendar events and meeting notes (optionally with transcripts), and schedule or edit events on a connected calendar.
• Lead search: company-first discovery from external databases, then import selected companies and contacts into the CRM. Zero lists a lead database of 350M+ contacts.
• Outreach sequences: create and edit inactive sequence drafts, review generated messages and enrolled contacts, and activate only from an explicitly approved activation plan.
• Lists, reports and dashboards: manage regular and dynamic lists, run saved reports and build dashboard panels.
• Workspace context: load and edit AI contexts such as ICP definitions, scoring criteria and writing style.
• Workspace-scoped OAuth: each connection is bound to the single workspace you authorize.

According to Zero's docs, the tools include find_deals, find_contacts, add_contact, edit_deal, find_company_activities, lead_search_companies and sequences_create_draft. Your client receives the full list and parameters automatically when it connects.

Use cases of Zero MCP Server

• Pipeline review: "Show me all deals closing this month and flag any with no activity in two weeks."
• Quick data entry: "Create a new contact for Jane Smith at Acme Corp and add a note to the Acme deal."
• Meeting prep: pull a company's activity timeline and Zero's meeting brief before a call.
• Prospecting: "Find companies in the technology industry that match our ICP" with lead search, then import the best matches to a list.
• Outbound drafts: draft a sequence and its messages for review, then activate it once you approve the plan.
• Reporting: run a saved pipeline report and summarize what changed this week.

Troubleshooting Zero MCP Server

• The assistant uses the wrong fields or stages: have it call get_instructions and get_workspace_metadata first; Zero's docs say the other tools depend on them.
• Data from the wrong workspace: the connection only reaches the workspace chosen during sign-in. Disconnect and reconnect to pick a different one.
• Worried about unwanted changes: set per-tool permissions in your client. Zero suggests allowing every find_* tool and requiring confirmation for anything that creates, updates or deletes.
• Email verification fails or stops: verify_contact_emails uses workspace credits, so check your remaining credits.