---
name: lots-crm
description: Run a LotsCRM sales workspace (contacts, companies, deals, pipelines, activity history and follow-ups) through its MCP server. Use when the user wants you to add leads, log conversations, move deals, plan follow-ups or report on their pipeline.
metadata:
  compatibility: Any compatible remote MCP client, including ChatGPT, Claude and coding agents
  author: lotstech
  version: "1.0"
  platform: lotscrm.com
  mcp_endpoint: https://api.lotscrm.com/mcp
---

# LotsCRM

You keep the user's sales book in LotsCRM: contacts, companies, deals on custom pipelines, the history of every conversation, and the follow-ups that are due. LotsCRM is the record. You do the work under the user's instructions, and the user reviews everything in the LotsCRM dashboard.

## Connect

Use `https://api.lotscrm.com/mcp` as a remote MCP server and sign in with a Lots account. If these tools are not connected, give the user that URL and the steps for their client (setup for common agents: https://lotscrm.com/mcp). An API key from https://www.lotstech.com/api is the alternative for clients that need one; never ask the user to paste a key or password into chat.

For REST, read `https://api.lotscrm.com/docs.md`. Use the connected server's tool schemas over any fixed list. [Tools reference](references/TOOLS.md) and [workflow examples](references/WORKFLOWS.md) are supporting guides.

## Start every session

1. `list_workspaces`, then pick the workspace the user means. Each workspace is a separate sales book (an agency keeps one per client), so never carry records, context or assumptions from one workspace to another.
2. `get_crm_briefing` for that workspace. It returns your role, the pipeline setup, current sales priorities, and the workspace's business context in two labelled parts: public business facts, and private guidance that is for you only.
3. Work within your role. Owner: everything. Admin: team, pipelines and settings. Manager: edit and archive any record. Member: create and edit records. Viewer: read only.

## Operate

- **Creates and imports need an `idempotency_key`.** Use a stable key per intended record (for example `contact:jane@example.com`). Retrying with the same key returns the original result; the same key with different data is refused (409), so make a new key only for a genuinely new record.
- **Deals use `expected_version`.** Read the deal, pass its version on `update_deal`, `move_deal` and `archive_deal`. A conflict means someone changed it: read again and reconcile, do not overwrite. Use `move_deal` for stage changes; won or lost status follows the stage, and a lost deal needs `lost_reason`.
- **Contacts and companies are deduplicated** in a workspace by email and domain. Search first (`search_crm`) and update rather than create a near-duplicate. `bulk_upsert_prospects` imports 1 to 100 rows, keeps each row's source and source_url, and reports row errors; report them to the user.
- **`custom_fields` merge:** keys you send overwrite, keys you leave out stay, a key set to null is removed.
- **Archive, never delete.** Archive tools are recoverable and keep history. There is no hard delete through MCP.
- **Log what happened.** `record_activity` records a call, meeting, email, message or note after it happens. It never sends anything.
- **Follow-ups schedule work.** `create_follow_up` and `update_follow_up` set due tasks; they do not send reminders or outreach.

## Drafting and outreach

LotsCRM never sends emails or messages. When the user wants a message about a deal, call `prepare_follow_up` with the deal (or `get_deal_brief` before a call); for a contact without a deal, read `get_contact` and `get_timeline` and check its consent and marketing status first. Draft only from the CRM history and the public business facts. If it returns `can_contact: false` (opted out or do not contact), do not draft outreach; tell the user why. Send with the tools the user already uses, only when they ask, then log it with `record_activity`. Never quote private guidance to a customer or in public copy, and never invent facts, prices or customer results.

## Reports

`get_sales_brief` gives today's priorities, `get_pipeline_summary` gives counts, value and weighted value per stage and currency (never add different currencies together), `list_follow_ups` shows due and overdue work, and `get_timeline` shows recent history for a record.

## Billing

Each active workspace is capacity. A plan covers a number of workspaces; workspaces beyond it are paid from the owner's credits automatically, charged daily at the plan's rate, or at the pay-as-you-go rate without a plan. Use `get_billing` for the current plan, coverage, credit balance and exact rates; do not quote prices from memory. When a workspace is not funded, reads and exports keep working and writes are refused until it is funded again; nothing is deleted. `create_checkout` returns a link the user opens to pay or add credits in their browser; never ask for card details in chat. A return to the site after checkout does not prove payment: check `get_billing` again. Purchased credits never expire and work across Lots products. The user's AI provider bills its own AI usage.