Connect

MCP server

Connect Zoye to any MCP-compatible AI assistant through the Model Context Protocol. Once added, you can ask your assistant - Claude Code, Cursor, Windsurf, Cline, Zed, and others - to create, update, and search Zoye contacts in plain language. Setup takes about a minute.

What is MCP?

The Model Context Protocol is an open standard that lets AI assistants call external tools. Because it is a standard, the Zoye MCP server is tool-agnostic: you configure it once and it works the same in every MCP-compatible client. The server exposes your contacts API as a set of tools your assistant can invoke directly, so it can manage Leads for you without leaving the editor.

Use a secret key

The MCP server runs on your own machine, so give it a secret key (zk_live_...) to unlock create, update, and search. Keep the key in an environment variable, never commit it to source control.

Add to Claude Code (one command)

Run one command. It registers Zoye and pins your key as an env var:

Terminal

claude mcp add zoye -e ZOYE_API_KEY=zk_live_YOUR_KEY -- npx -y @zoye/mcp

That is it. Start a new Claude Code session and the Zoye tools are available.

Add to any other MCP client

Every other MCP client - Cursor, Windsurf, Cline, Zed, and more - reads the same standard config. Add this block under mcpServers in your client's MCP settings file (for example ~/.cursor/mcp.json for Cursor, the MCP settings panel in Windsurf, or cline_mcp_settings.json for Cline):

MCP config (works in any MCP client)

JSON

{
  "mcpServers": {
    "zoye": {
      "command": "npx",
      "args": ["-y", "@zoye/mcp"],
      "env": {
        "ZOYE_API_KEY": "zk_live_YOUR_KEY"
      }
    }
  }
}

The only things that ever change between tools are where the config file lives and how you open it - the server entry itself is identical.

Using an AI app builder instead? (Lovable, Bolt, Replit, v0, base44, ...)

App builders generate an app rather than act as an MCP client, so they do not use the config above. They can still sync to Zoye in one step - point them at the REST API. Tell the builder, in plain words:

"When a user signs up, POST their name, email, phone and company to https://api.zoye.io/public/v1/contacts with the header Authorization: Bearer zk_pub_YOUR_KEY."

That is all most builders need. See the REST API page for the full request shape, and use a publishable key (zk_pub_...) when the call runs in the browser.

Available tools

Tool	What it does
create_contact	Create a single person or company lead.
update_contact	Update fields on an existing contact by id.
get_contact	Fetch one contact by id.
search_contacts	Search contacts by free text or email.
create_contacts_batch	Create up to 100 contacts in one call.
zoye_whoami	Report the key type, scopes, and rate-limit tier.

Example prompts

Once connected, talk to your assistant naturally:

"Add Jordan Rivera, jordan@northwind.com, as a new lead from the website."
"Create company leads for Northwind, Brightwave, and Lumina with their websites."
"Search my Zoye contacts for anyone at Northwind."
"Update contact ctc_9aZ2bQ - set the position to Head of Ops."
"Which Zoye key am I using and what can it do?"

The MCP tools map one to one onto the REST API. If you want to wire Zoye into a non-MCP tool, the REST endpoints are the same capabilities under the hood.