Skip to content

Work in VivreCRM from your AI assistant

Connect Claude, Cursor, VS Code or any MCP client to your CRM. Ask about your pipeline, update records and send reports in plain language. It works with your own role, so it sees and changes only what you can.

Paste it into your assistant and sign in with your VivreCRM account. You don't need an API key.

Example conversation

Which deals close this month, and what are they worth?

VivreCRMsearch_deals

Four deals close before 31 October, worth ₹8,40,000 together.

DealStageValue
Northwind TradersNegotiation₹3,20,000
Kaveri FoodsProposal₹2,10,000
Bluepeak LogisticsProposal₹1,60,000
Saffron StudioQualified₹1,50,000

Northwind has had no activity in 12 days. Shall I add a follow-up task for Meera?

Set it up in your assistant

Pick the one you use. Each takes about a minute.

  1. In Claude on the web or desktop, open Settings, then Connectors.
  2. Choose Add custom connector. Name it VivreCRM and paste the server address.
  3. Choose Connect, sign in to VivreCRM and approve access. That's it.
Server address
https://mcp.vivrecrm.com/mcp

Things you can ask

Ask in your own words. The assistant chooses the tools and shows you what it did.

  • "Create a follow-up task for every lead nobody has contacted in two weeks."

    filter_recordscreate_task
  • "Where did this quarter's leads come from, and which source converts best?"

    get_leads_by_sourceget_pipeline_summary
  • "Merge the two contacts for Asha Rao and keep the newer phone number."

    search_contactsmerge_contacts
  • "Import this CSV from the trade show and tag everyone Expo 2026."

    import_recordsadd_tag_to_records
  • "Move every deal in Proposal with no reply in 30 days to Lost."

    search_dealsmark_deal_lost
  • "Email the sales team the pipeline report every Monday at 9."

    create_reportsend_report

Everything it can do

151 tools, covering the same work you do in the app.

Contacts, leads, deals and companies Find, create, update, merge and restore records, and move deals through their stages. 43
  • add_deal_participantPut a contact on a deal with a role: Champion, Decision Maker, Influencer, Blocker or End User.
  • assign_recordsGive a selection of leads or deals one owner (a user_id from list_members).
  • create_companyCreate a company.
  • create_contactCreate a contact.
  • create_dealCreate a deal from a contact (contact_id) or from one of its leads (lead_id: the lead's contact comes with it), never from a company.
  • create_leadCreate a lead for a contact, with its source, status and owner.
  • delete_companyDelete a company (to the trash), as the app's Delete does.
  • delete_contactDelete a contact (to the trash), with its leads and deals.
  • delete_dealDelete a deal (to the trash), as the app's Delete does.
  • delete_leadDelete a lead (to the trash), as the app's Delete does.
  • delete_recordsDelete a selection of contacts, leads, deals or companies (to the trash), as a list's bulk Delete does.
  • filter_recordsContacts, leads, deals, companies or tasks matching a condition tree, as the app's lists filter them.
  • get_companyOne company with all its fields, tags and custom fields.
  • get_contactOne contact, as the app's contact page has it: name, email and phone (main and secondary), job title, company, owner, custom fields, last activity.
  • get_dealOne deal with its contact or lead, pipeline, stage, value and owner.
  • get_leadOne lead, as the app's lead page has it: its contact, status, score, source and attribution, owner and custom fields.
  • list_company_contactsA company's contacts, newest first.
  • list_contact_dealsA contact's deals: its own, those made from its leads and those it is one of the people on, in every status.
  • list_contact_leadsA contact's leads, newest first.
  • list_deal_participantsThe people on a deal besides its contact: each one's contact and role.
  • list_dealsDeals, newest first, optionally by stage name, pipeline, owner or status (every status unless one is given).
  • list_field_valuesThe lists lead and company fields offer: lead status, source, medium, channel, platform, priority and campaign; company type.
  • list_lead_dealsThe deals made from a lead, every status, newest first.
  • list_leadsLeads, newest first, optionally by status or owner.
  • mark_deal_abandonedClose a deal as abandoned, with a reason: it moves to its pipeline's Abandoned stage, dated closed_at or today.
  • mark_deal_lostClose a deal as lost, with a reason: it moves to its pipeline's Lost stage, dated closed_at or today.
  • mark_deal_wonClose a deal as won: it moves to its pipeline's Won stage, dated closed_at or today in the organization's time zone.
  • merge_contactsMerge duplicate contacts into one: the duplicates' leads, deals, notes, tasks and tags move to the primary, and the duplicates go to the trash.
  • merge_leadsMerge duplicate leads of one contact into one: the duplicates' deals, notes, tasks and tags move to the primary, and the duplicates go to the trash.
  • remove_deal_participantTake a person off a deal.
  • reopen_dealReopen a won, lost or abandoned deal: it goes back to the open stage it closed from, or its pipeline's last open stage; the close date and reason are cleared.
  • restore_recordBring a deleted contact, lead, deal or company back from Trash, by the id it had.
  • searchThe app's search: text across contacts, leads, deals, companies and notes, best match first.
  • search_companiesFind companies by name, or list them newest first when q is empty.
  • search_contactsFind contacts by name, email or phone (main or secondary).
  • search_dealsFind deals by title, their contact's name, email or phone, stage name or currency, as the app's deals search does.
  • search_leadsFind leads by contact name, email or phone, optionally by status or owner.
  • update_companyChange a company's fields; only the fields given change.
  • update_contactChange a contact's fields; only the fields given change.
  • update_dealChange a deal's fields; only the fields given change: title, value, currency, expected close date, owner (assigned_to_id), custom fields, its contact or lead (one of the two), or its pipeline with a stage of that pipeline.
  • update_field_valuesSet the whole list a lead or company field offers, in order.
  • update_leadChange a lead's status, score, owner, source or other fields; only those given change.
  • update_leads_statusSet one status on a selection of leads: a lead status of this organization (describe_organisation).
Tasks and notes Plan the follow-ups, tick them off, and keep notes on any record. 21
  • add_noteAdd a note to a contact, lead, deal, company or task.
  • complete_taskMark a task done, as its checkbox in the app does.
  • complete_tasksMark a selection of tasks done.
  • create_taskCreate a task, optionally linked to a record (shown in its activity).
  • create_task_priorityMake a task priority of the organization's own, beside the built-in ones.
  • create_task_typeMake a task type of the organization's own, beside the built-in ones.
  • delete_noteDelete a note: its writer or an admin may.
  • delete_taskDelete a task (to the trash), as the app's Delete does.
  • delete_task_priorityDelete a task priority of the organization's own.
  • delete_task_typeDelete a task type of the organization's own.
  • get_activity_feedThe latest activity across the CRM that you can see, newest first.
  • get_taskOne task: title, type, priority, status, due date, assignee and the record it is linked to.
  • list_activitiesA record's activity timeline (calls, emails, stage changes, edits), newest first.
  • list_notesThe notes on a record, newest first.
  • list_task_prioritiesThe organization's task priority list: built-in and its own, each with whether it is switched off.
  • list_task_typesThe organization's task type list: built-in and its own, each with whether it is switched off.
  • list_tasksTasks you can see, newest first, optionally by status, assignee, linked record or due dates.
  • update_noteChange a note's text.
  • update_taskChange a task's fields; only the fields given change.
  • update_task_priorityRename a task priority of the organization's own, or switch a built-in one off or on (active).
  • update_task_typeRename a task type of the organization's own, or switch a built-in one off or on (active).
Pipelines and setup Shape the CRM itself: pipelines, stages, custom fields, tags, task types and priorities. 30
  • add_tagPut a tag on a record.
  • add_tag_to_recordsPut a tag on a selection of contacts, leads, deals or companies.
  • create_custom_fieldMake a custom field for contacts, leads, deals or companies.
  • create_pipelineMake a pipeline.
  • create_stageAdd an open stage to a pipeline: after its last open stage, before Won, Lost and Abandoned, unless order places it.
  • create_tagMake a tag for the organization.
  • delete_custom_fieldDelete a custom field and every value records hold in it.
  • delete_pipelineDelete a pipeline that holds no deals.
  • delete_stageDelete an open stage that holds no deals; a pipeline keeps at least one open stage.
  • delete_tagDelete a tag: it comes off every record.
  • describe_organisationThis organization's own setup, to use before creating or changing records: your role and access here, its time zone, pipelines with their stages (ids, types), lead statuses, the attribution values it uses, custom fields per record kind (id, name, type, options, required), task types and priorities, company types, currencies and the people records can be assigned to.
  • get_guideThe guide to working in Vivre CRM through these tools, a topic at a time: which record is made from which, lead fields and attribution and custom fields, deals and pipelines, tasks, roles, values, refusals, finding records, CRM settings, reports, saved views and automations, imports, and the CRM's webhooks and Slack routes.
  • list_custom_fieldsThe organization's custom fields, in their order, optionally for one kind of record: id, name, type, options, required, state.
  • list_filter_fieldsThe fields a kind of record can be filtered by, as the app's filter panel offers them: key, label, type, choices, whether it can be empty, and the organization's custom fields (key cf__<name>).
  • list_membersThe organization's people a record can be assigned to: user_id and name.
  • list_organisationsThe organizations this connection can work in, each with its id and access (read, or read_write).
  • list_pipelinesThe organization's pipelines, each with its stages in order (name, type, probability).
  • list_tagsThe organization's tags, or the tags on one record when entity_type and entity_id are given.
  • move_deals_to_stageMove a selection of deals to one stage (a stage_id from list_pipelines).
  • preview_custom_field_retypeWhat changing a custom field's type would do to the values records hold: how many convert and which do not.
  • remove_tagTake a tag off a record.
  • remove_tag_from_recordsTake a tag off a selection of contacts, leads, deals or companies.
  • retype_custom_fieldChange a custom field's type, after preview_custom_field_retype and the person's yes: a field of the new type takes its place and its values move onto it; one that does not convert is left empty, set to default, added as an option, or stops the move (on_failure).
  • update_custom_fieldRename a custom field, change a select field's options, or make it required.
  • update_custom_field_orderPut one kind of record's custom fields in the order forms show them: every active field of that kind, once.
  • update_deal_stageMove a deal to another stage of its pipeline, by stage name, as the app's deal form does.
  • update_pipelineRename a pipeline, or make it the default.
  • update_stageRename an open stage, or change its colour or probability.
  • update_stage_orderPut a pipeline's open stages in a new order: every open stage, once.
  • update_tagRename a tag or change its colour; every record keeps it.
Reports, views and numbers Ask for the numbers, save the views you use, and send reports on a schedule. 22
  • copy_saved_viewCopy a view you can open into a new one of yours, with the same setup (members copy into personal only).
  • create_reportMake a report from get_report_schema's columns and filters, over a period.
  • create_saved_viewSave a view of the leads list.
  • delete_reportDelete a report, and its schedule with it.
  • delete_saved_viewDelete a saved view.
  • get_dashboard_summaryThe dashboard's figures for a period, as you can see them: leads, deals won and their value, open deals, tasks.
  • get_leads_by_sourceLeads per source for a period, as the dashboard's chart shows them.
  • get_org_metricsThe stats strip of each list (contacts, leads, deals, companies and tasks), as you can see them.
  • get_pipeline_summaryThe dashboard's pipeline chart: open deals per open stage of a pipeline (count and value per currency).
  • get_record_statsThe figures a list shows above it, as you can see them (for deals: total, open, open value, won this month, closing this month).
  • get_reportOne report: its columns, filters, period, schedule and last run.
  • get_report_schemaThe columns and filters a report can use, per kind of record (owners and admins).
  • get_reports_healthScheduled reports that failed or partly failed in the last 7 days, and the latest error.
  • get_saved_viewOne saved view: its name, whether it is personal or the organization's, its setup and whether you may change it.
  • list_report_runsA report's runs, newest first: when, how, how many rows, and any error.
  • list_reportsThe organization's reports, with their columns, filters, period and last run (owners and admins).
  • list_saved_viewsThe saved views of the leads list you can open: your personal ones and the organization's, each with its filter, columns, sort and quick-view chip.
  • open_saved_viewThe leads a saved view shows, as the leads list opens it: its filter and its quick-view chip together, in its order, as you may see them.
  • run_reportRun a report now and read it: its columns, the first rows (limit, 100 unless given) and how many rows there are.
  • send_reportEmail a report now.
  • update_reportChange a report's name, columns, filters or period.
  • update_saved_viewRename a view or change its setup.
Automations Set up the rules that act on their own, and see what they did. 7
  • create_automationMake an automation from get_automation_catalogue's triggers and actions.
  • delete_automationDelete an automation and its run history.
  • get_automationOne automation, with its last run.
  • get_automation_catalogueWhat an automation can be made of, per kind of record: its triggers, and the actions it can take with their inputs; and how many may be switched on and run a day on the plan.
  • list_automation_runsAutomation runs, newest first: one automation's (id) or every automation's, with each run's status, steps and reason.
  • list_automationsThe organization's automations: trigger, conditions, actions, on or off, last run.
  • update_automationChange an automation, or switch it on or off (is_active).
Imports, webhooks and integrations Bring records in from a file, send events out to your systems, and route alerts to Slack. 28
  • create_webhook_endpointMake a CRM webhook endpoint: an https URL and a label, and the events to send it.
  • delete_webhook_endpointDelete a CRM webhook endpoint; it is sent nothing more.
  • get_importOne import job: status (pending, processing, done, failed, paused), rows in total, imported and skipped, and any error.
  • get_inbound_payloadOne payload: what came in, what it mapped to, the record it made, and each try.
  • get_inbound_replayHow far a replay has got: its total, and how many succeeded, failed or are still running.
  • get_inbound_sampleAn inbound token's latest payload and every key its recent payloads carried, with a suggested mapping.
  • get_inbound_statsHow many of an inbound token's payloads ended each way (success, failed, held...).
  • get_inbound_tokenOne inbound token, with its field mapping.
  • get_webhook_endpointOne CRM webhook endpoint, with the events it is sent.
  • import_recordsImport rows of contacts, leads, companies or deals as the app's import wizard does: the same column suggestions, matching (an email or phone finds a contact or lead; a company by name), record limits and skip reasons.
  • import_remaining_rowsImport the rows an older import left past its row limit, as a new job.
  • list_import_rowsAn import's rows: each one's outcome (added, skipped, pending) and, for a skipped row, why.
  • list_importsImport jobs, newest first: what was imported, its status and counts.
  • list_inbound_payloadsAn inbound token's payloads, newest first: each one's status, the record it made and the fields that did not map.
  • list_inbound_tokensThe CRM's inbound webhooks: tokens other systems post leads or contacts to, with each one's label, state (active, paused: payloads held, off: refused), the record it makes and its field mapping.
  • list_slack_routesWhich CRM notifications go to which Slack channel: each channel (added by the organization in its Main settings) with its CRM notifications, and every one it can be sent.
  • list_webhook_deliveriesA CRM endpoint's deliveries, newest first: each event sent, its status and tries.
  • list_webhook_endpointsThe CRM's outbound webhook endpoints: where the CRM sends its events (label, URL, on or off, circuit state).
  • list_webhook_eventsThe events a CRM webhook endpoint can be sent.
  • replay_inbound_payloadsRun an inbound token's held and failed payloads again with its current mapping, or only payload_id.
  • rerun_importRun an import's file again as a new job, with the same mapping.
  • resume_importCarry on a paused import from where it stopped.
  • retry_webhook_deliverySend a failed, dead or cancelled delivery again now.
  • send_webhook_testSend a CRM endpoint a test event now and say what it answered.
  • update_inbound_mappingSet how an inbound token's payload fields fill the record it makes: field_mapping {field key: payload key, or {source, formula, default, value_map}}.
  • update_inbound_tokenRename an inbound token or change its status: active, paused (payloads are held until it is active again) or inactive (payloads are refused).
  • update_slack_routeChoose the CRM notifications a Slack channel is sent; its organization notifications are left as they are.
  • update_webhook_endpointChange a CRM webhook endpoint: its label, URL, events, or switch it off and on (is_active).

You stay in control

The assistant works as you, inside the limits you already have.

Your role, nothing more
It acts with your role in each organization. A viewer's assistant can only read.
Read-only if you prefer
Give a connection read access only, and it can look but never change anything.
Every change is labelled
Changes show in the activity feed as made via the app's name, and you can filter by it.
One organization at a time
Each request names one organization. Records never cross from one to another.
Disconnect any time
Remove the app under Connected apps in VivreCRM and its access ends at once.
Asks before it deletes
It is told to confirm with you before deleting, or before changing many records at once.

Technical details

Address
https://mcp.vivrecrm.com/mcp
Transport
Streamable HTTP, JSON responses, stateless
Protocol
MCP 2026-07-28
Sign-in
OAuth, with dynamic client registration
Metadata
https://mcp.vivrecrm.com/.well-known/oauth-protected-resource/mcp

Included in Pro

MCP comes with the Pro plan. Try VivreCRM free, then upgrade when you want to connect your assistant.