AgencyZoom MCP by usefulapi

WRITE: add a note to a customer's activity feed (visible to the agency's users; AgencyZoom does not send it to the customer). Not idempotent: calling twice adds two notes. POST /v1/api/customers/{customerId}/notes.

WRITE: add a note to a lead's activity feed (visible to the agency's users; AgencyZoom does not send it to the customer). Not idempotent: calling twice adds two notes. POST /v1/api/leads/{leadId}/notes.

WRITE: mark a task as completed. Repeated calls may repeat notifications or automations; undo with agencyzoom_reopen_task. PUT /v1/api/tasks/{taskId}/completed.

WRITE: create a new sales lead in a pipeline stage. AgencyZoom requires the pipeline and stage (agencyzoom_list_pipelines), first name, e-mail, lead source, assigned producer and country. Creating a lead can trigger the agency's own automations (assignment, tasks, e-mails) in AgencyZoom. Not idempotent: calling twice creates two leads, so search first (agencyzoom_search_leads by e-mail or phone). POST /v1/api/leads/create.

WRITE: open a service ticket for a customer in a service pipeline stage. Needs the pipeline and stage (agencyzoom_list_pipelines with type 'service'), a priority and a category (agencyzoom_list_service_ticket_options). The assigned CSR may be notified, and the agency's service automations can run. Not idempotent: calling twice opens two tickets. POST /v1/api/serviceTicket/service-tickets/create.

WRITE: create a task (to-do, call, e-mail or meeting) linked to a lead or customer, optionally assigned to an employee. The assignee may be notified by AgencyZoom. Link it with lead_id or customer_id (or contact_email, which AgencyZoom matches to a lead or customer). Not idempotent: calling twice creates two tasks. POST /v1/api/tasks.

One customer by id with full details: contact data, address, source, agent, CSR, custom fields and policy summary. GET /v1/api/customers/{customerId}.

The policies written through AgencyZoom for a customer: type, carrier, policy number, premium (cents), items, sold/effective/expiry dates, agent, CSR and status (0 cancelled, 1 active, 3 upcoming, 4 renewed, 10-13 active variants). GET /v1/api/customers/{customerId}/policies.

The tasks linked to a customer (open, done, cancelled) with due date, assignees and notes. GET /v1/api/customers/{customerId}/tasks.

One lead by id with full details: contact data, address, status, stage, source, assigned producer and CSR, premiums (cents), dates and custom fields. GET /v1/api/leads/{leadId}.

The activity notes of a lead: type (note, e-mail, creation...), date, author, title and body. GET /v1/api/leads/{leadId}/notes.

The opportunities (quoted lines of business) of a lead: carrier, product line, premium, items, status and property address. GET /v1/api/leads/{leadId}/opportunities.

The tasks linked to a lead (open, done, cancelled) with due date, assignees and notes. GET /v1/api/leads/{leadId}/tasks.

The dashboard sales summary for the agency or one producer: goals, month-to-date and today's sales, trending, and daily premium/revenue/items/policies for the period. Amounts are in cents. Read-only (a POST in AgencyZoom). POST /v1/api/dashboard-data/sales-data.

One task by id: title, status, due date, assignees, notes and the customer or lead it belongs to. GET /v1/api/tasks/{taskId}.

The insurance carriers configured in the agency (id, name, standard carrier code). GET /v1/api/carriers.

The agency's employees: id, name, e-mail, phone, whether producer, active or owner. Use the ids to assign leads and tasks. GET /v1/api/employees.

The lead sources (id, name, category, whether sales from it count as sales). GET /v1/api/lead-sources.

The sales (lead) or service pipelines with their stages and ids. Needed to create leads or service tickets and to move a lead between stages. GET /v1/api/pipelines-and-stages.

The policy types / product lines (id, name, category, standard product line code), for policy filters. GET /v1/api/product-lines.

The service ticket categories and priorities (id, name), needed to create a service ticket. GET /v1/api/service-categories and GET /v1/api/service-priorities.

The tags defined in the agency (id, name). GET /v1/api/tags.

WRITE: move an active lead (a status check refuses leads already won, lost or x-dated) to another stage of a lead pipeline (workflow_id and workflow_stage_id from agencyzoom_list_pipelines). The lead stays active: it does not mark the lead won, lost or x-dated. Moving into a stage can trigger the agency's automations. The read and update are not atomic: a concurrent status change can be overwritten and reactivate a lead. Do not use while another process changes the same lead. Automations may repeat on repeated calls. PUT /v1/api/leads/{leadId}/stage.

WRITE: reopen a completed task, optionally with a comment. Repeated calls may repeat notifications or automations. PUT /v1/api/tasks/{taskId}/reopened.

Search customers (clients with at least one written policy) with filters; returns contact details, address, source, agent and a policy summary, paged. First/last name match partially. POST /v1/api/customers.

Search sales leads in AgencyZoom with filters; returns name, contact details, status, pipeline stage, source, assigned producer, quoted and sold premium (in cents) and dates, paged. Names, e-mail and phone match by prefix. Use agencyzoom_list_pipelines for workflow/stage ids and agencyzoom_list_employees for producer ids. POST /v1/api/leads/list.

Search service tickets (client service requests) by household name, status, category, priority, policy number and created/completed dates, paged. POST /v1/api/serviceTicket/service-tickets/list.

Search tasks across the agency: by status (open/completed), assignee, period (today, past due, next week...), type and creation date; returns title, due date, assignees, linked customer or lead and notes, paged. POST /v1/api/tasks/list.