Guides

Connect an assistant (MCP)

Point Claude — or anything else that speaks the Model Context Protocol — at the account and ask in words what you would otherwise look up.

Same key, same scopes, same limits as the REST API: a key that cannot read customers cannot be asked about them either.

https://api.zinevu.com/api/mcp

Authenticate with the same Authorization: Bearer header. The server speaks the stateless 2026-07-28 revision and the older handshake-based ones, so a client that only knows initialize works unchanged.

The tools#

Seven, all read-only:

whoami — the account and what this key may do.
search_leads and get_lead
search_offers and get_offer
search_customers and get_customer

Nothing here writes, sends or changes anything — an assistant can read the pipeline and nothing it does can cost you a lead or an e-mail. Only the tools your key's scopes allow are listed, and calling one by name without the scope is refused just the same; the refusal names the scope so you know which one to add.

Configuring a client#

claude_desktop_config.json

{  "mcpServers": {    "zinevu": {      "type": "http",      "url": "https://api.zinevu.com/api/mcp",      "headers": { "Authorization": "Bearer zv_live_..." }    }  }}

What an assistant is good at here

Questions that would otherwise be a report: which offers have been sitting unsigned the longest, what a customer asked for last spring, whether a lead already exists for this address. For anything that has to happen on a schedule or be exactly right every time, write the integration — an assistant is a reader, not a cron job.