An Agile CRM MCP that covers the whole record, not just contacts
Connect your Agile CRM domain, login email and REST API key, and 60 nodes land on the canvas: find and write contacts and companies, move deals through tracks, open and close tasks, log notes and events, and enroll people in campaigns. Every node runs on a schedule or from another app's event, chains with every other connector in one workflow, and keeps the key in your workspace rather than in one person's config file.
What the Agile CRM MCP connector does
The Agile CRM connector for Mattering Automations is 60 nodes over the vendor's REST API: 17 contact nodes, 5 company nodes, 11 deal nodes, 8 task nodes, 7 note nodes, 5 event nodes, 4 track nodes and 3 campaign nodes. That splits 23 read nodes and 37 action nodes, with 9 flagged destructive. One credential covers all of it, and it is three values rather than one, because Agile CRM authenticates with HTTP Basic using your login email as the username and the REST API key as the password, against your own account subdomain.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can look someone up with Agile CRM: Find Contact by Email, record what was discussed with Agile CRM: Create Contact Note, and open the next step with Agile CRM: Create Task, without anyone signing in to Agile CRM.
We could not find an MCP server published by Agile CRM itself. Its developer documentation is a REST reference and mentions none, so if you have been searching for an official one, this connector is the answer to that search rather than a competitor to one. What it gives you is the shape a CRM automation actually needs: typed nodes with pickers for deals, tracks, tasks and campaigns, destructive operations flagged so they can be gated, the credential held once in a shared workspace, and the whole surface usable as canvas steps as well as over MCP.
Two structural facts about this API are built into the connector rather than left for you to discover. Agile CRM answers in XML by default, so Mattering sends the JSON accept header on every single call, which is the difference between a usable response and an unparseable string. And there is no PATCH verb anywhere in this API: partial updates arrive as PUT on some paths and POST on others, with three different behaviours between them, so every node says which one it is and what it does to the fields you did not send.
One connection, three surfaces
- Visual automations. Drag Agile CRM nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Agile CRM node, ready to drop on the canvas
60 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 23
Agile CRM: Filter Contacts and Companies
Query contacts or companies with Agile's rule-based filter. This is the only documented way to select records by tag, by custom-field value or by an updated-time window - the plain list endpoint offers no filtering at all, so an incremental sync is built here. A rule is {LHS: field, CONDITION: operator, RHS: value}; contact_type picks PERSON or COMPANY. Sent form-encoded with the filter serialized as JSON text. Read-only despite the POST verb.
Agile CRM: Find Contact by Email
Fetch the contact stored against an exact email address. This is an EXACT, CASE-SENSITIVE match, not a search - Alex@example.com and alex@example.com are different addresses to Agile. Returns 204 with an empty body when nothing matches, which is the idiomatic way to check whether a contact already exists before creating one.
Agile CRM: Find Contact by Phone Number
Fetch the contact stored against a phone number. Matching is exact on the stored string, so a number saved with punctuation will not be found by the digits alone. Returns 204 with an empty body when nothing matches. Useful for inbound-call workflows.
Agile CRM: Get Company
Fetch one company by id. Shares the /contacts/{id} path with Get Contact because Agile keeps both in one table; this node exists so the id field asks for a company. Returns 204 with an empty body when nothing matches.
Agile CRM: Get Contact
Fetch one contact by its numeric id. Returns 204 with an empty body when no contact has that id, which surfaces as a successful node with empty data rather than as an error.
Agile CRM: Get Deal
Fetch one deal by id, with its related contacts, owner and custom_data embedded.
Agile CRM: Get Task
Fetch one task by id, with its related contacts and owner embedded.
Agile CRM: List Campaigns
List the account's marketing campaigns. Agile calls them workflows on the wire, which is why the campaign id a contact is enrolled with is called workflow-id. Each entry also carries a large 'rules' string holding the whole campaign definition as escaped JSON - useful to nobody downstream, and large, so read data[].id and data[].name and leave it alone. This is what fills the campaign pickers.
Agile CRM: List Companies
List companies. Read-only despite the POST verb: Agile takes the paging parameters as form fields rather than on the query string. Same cursor convention as the contact list - the next-page cursor is grafted onto the LAST element of the returned array. A company's name lives inside the properties array as the SYSTEM property named 'name', not at the top level.
Agile CRM: List Contacts
List contacts in the account, newest-created first. Paged with page_size and cursor. Agile returns a plain JSON array with no envelope: the record count is grafted onto the FIRST element and the next-page cursor onto the LAST element, so a paging loop has to carry the cursor forward by hand. A contact's name and email live inside the properties array, not at the top level. This is also the connector's auth probe: an invalid credential answers 401 here.
Agile CRM: List Deals
List every deal in the account, newest-created first, with the related contacts embedded. Same cursor convention as the contact list: the count rides on the first element and the next-page cursor on the last. Deals are the one CRM entity Agile returns with a top-level name, which is what lets the deal pickers elsewhere in this connector show readable labels.
Agile CRM: List Deals Grouped by Milestone
List a track's deals GROUPED BY MILESTONE - the board view, in other words. Pass pipeline_id 0 for the default track. Note the output shape: this returns an OBJECT keyed by milestone name, not an array, so downstream paths have to name a milestone literally (data.Prospect[].name) and a chart consumer will not find rows to fan out over. Use List Deals in Track when you want a flat list.
Agile CRM: List Deals for Contact
List the deals related to one contact. Unpaged: it returns whatever is linked to that contact.
Agile CRM: List Deals in Track
List the deals on one track, as a flat paged array. Two magic values are documented: pipeline_id 0 means the account's default track, and pipeline_id 1 means every deal on every track. Same cursor convention as the other lists.
Agile CRM: List Events
List calendar events inside a time window. BOTH bounds are mandatory and both are epoch SECONDS - there is no way to ask for all events, which is why nothing in this connector offers an event picker. Returns a flat array with the related contacts embedded.
Agile CRM: List Events for Contact
List the events related to one contact, sorted by date. Takes no time window, so this is the way to see a contact's whole calendar history.
Agile CRM: List Notes for Contact
List the notes attached to one contact. Unpaged. This is also what fills the note picker on Delete Note from Contact.
Agile CRM: List Notes for Deal
List the notes attached to one deal. Unpaged.
Agile CRM: List Tasks
List every task in the account, newest-created first, with related contacts and the task owner embedded. This endpoint documents no parameters at all - no paging, no filter - so use List Tasks by Filter when the account has many tasks. It is what fills the task picker elsewhere in this connector.
Agile CRM: List Tasks by Filter
List tasks filtered by category, status or priority, and optionally limited to pending ones. The pairing is strict: the criteria you choose decides which values type may take, and a mismatched pair returns nothing rather than an error. This also covers 'what is due' - set pending true - which is why the separate pending-tasks-by-days endpoint is not built as its own node. Paged with page_size and cursor, same cursor convention as the other lists.
Agile CRM: List Tasks for Contact
List the tasks related to one contact, most recent first. Unpaged.
Agile CRM: List Tracks
List the account's tracks - Agile's word for deal pipelines - each with its milestones. Read this before writing any deal: milestones come back as ONE COMMA-SEPARATED STRING per track ("Open,New,Prospect,Proposal,Won,Lost"), and Agile matches milestone names case-sensitively, so this is where the exact spelling comes from. It is also what fills the track pickers on the deal nodes.
Agile CRM: Search Contacts and Companies
Free-text search across a contact's or company's default fields and any custom fields marked searchable in Agile. All three parameters are mandatory per the vendor's docs, including the PERSON / COMPANY switch - one call cannot return both. This endpoint has no cursor, so page_size is the whole result set.
Action nodes 37
Agile CRM: Add Tags by Email
Find the contact with this exact email address and add tags to it, without needing the contact id first. Additive. Sent form-encoded, with the tag list serialized as JSON text into the form value - supply a real list here and the connector does that for you. Answers 204 with no body, so it returns no contact to chain from.
Agile CRM: Add Tags to Contact
Add one or more tags to a contact by id. Additive: existing tags are kept. Tag names are case-sensitive, must start with a letter, and may only contain letters, digits, underscores and spaces. Reversible with Remove Tags from Contact. Returns the updated contact.
Agile CRM: Adjust Contact Score by Email
ADJUST a contact's lead score by a delta, keyed on email. This adds to the existing score rather than replacing it, and a negative number subtracts - which is what a behavioural scoring workflow wants. Use Set Contact Lead Score when you want an absolute value instead. Sent form-encoded. Returns the updated contact.
Agile CRM: Bulk Delete Deals
PERMANENTLY delete several deals at once, by id. Same irreversibility as Delete Deal, multiplied: there is no trash and no restore endpoint, and no partial-failure report - the call answers 200 for the batch. Wire-shape warning: Agile's own documentation contradicts itself here, sending a raw JSON body under a form-encoded content type. This node reproduces the documented request exactly rather than guessing, so if it misbehaves that is the first thing to check.
Agile CRM: Bulk Delete Notes
PERMANENTLY delete note records by id. Agile documents this under the deal-notes section but the path is the contacts one, and it takes note ids either way. There is no trash and no restore endpoint, and it answers 204 with an empty body, so nothing here can bring a note back. Sent form-encoded with the id list serialized as JSON text.
Agile CRM: Change Contact Owner
Reassign a contact to a different Agile user, named by that user's email address. Both fields are mandatory. If no user in the account has that email, Agile answers 200 with a message saying the user does not exist rather than with an error status, so check the body rather than the status code. Reversible by calling it again with the previous owner.
Agile CRM: Create Company
Create a company. Agile stores companies in the same table as contacts, so this posts to the contacts endpoint with type set to COMPANY - the node sends that for you. The company's name goes in as the SYSTEM property named 'name'. Lead score and star value do not apply to companies. No duplicate check is documented, so a retry creates a second company.
Agile CRM: Create Contact
Create a person. Agile has no documented duplicate check on this endpoint, so calling it twice with the same email creates two contacts; use Find Contact by Email first if a workflow can retry. first_name is mandatory inside properties. Do not send null values: Agile's docs say to omit the field or send an empty value instead. Returns the created contact with its new id. A 406 means the account's contact limit is reached.
Agile CRM: Create Contact Note
Create a note and attach it to one or more contacts in the same call. Both subject and description are mandatory. Returns the note with its new id, which is what makes this the note node to use in a chain - there is no update endpoint for a contact note, so a correction means deleting and re-creating.
Agile CRM: Create Deal
Create a deal. This endpoint is an UPSERT, not a pure create: Agile's docs state that if the posted data includes a valid deal id, that deal is UPDATED instead - so never template an id in here unless you mean it. name and expected_value are mandatory. The milestone must match a milestone on the chosen track exactly, including case, or the deal is created but does not appear in the milestone view. Returns the created deal with its new id.
Agile CRM: Create Deal Note
Create a note and attach it to one or more deals. Deal notes are a separate surface from contact notes and, unlike them, can be edited afterwards with Update Deal Note.
Agile CRM: Create Deal for Contact by Email
Create a deal already linked to the contact with this email address, saving a lookup. If no contact has that address Agile creates NO deal at all - so a silent no-op here means the email did not match, not that the deal failed. Same upsert caveat as Create Deal: a valid deal id in the body updates that deal instead.
Agile CRM: Create Event
Create a calendar event. title, start and end are mandatory, and the times are epoch SECONDS. Colour is Agile's priority signal rather than decoration: red for high, #36C for normal, green for low. Returns the created event with its new id.
Agile CRM: Create Task
Create a task. subject, type, priority_type and due are the mandatory fields, and all the enumerated values are CASE-SENSITIVE - Agile takes MEETING, not Meeting. due is epoch SECONDS. Returns the created task with its new id.
Agile CRM: Create Task for Contact by Email
Create a task already linked to the contact with this email address, saving a lookup when a webhook only carries an email. Same mandatory fields and case-sensitive vocabularies as Create Task.
Agile CRM: Create Track
Create a deal track with its milestones. Two documented rules: the name must not be "Default", and milestones go in as one comma-separated string, not a list, with every milestone's first letter capitalised. Returns the created track with its new id.
Agile CRM: Delete Company
PERMANENTLY delete a company. Agile's REST documentation describes no trash, restore or undelete endpoint, and answers 204 with an empty body, so nothing in this connector can bring the record back. What happens to the people whose contact_company_id pointed at it is not documented, so check the affected contacts afterwards.
Agile CRM: Delete Contact
PERMANENTLY delete a contact. Agile's REST documentation describes no trash, recycle bin, restore or undelete endpoint for contacts, and returns 204 with an empty body, so nothing in this connector can bring the record back - its notes, tasks, deals links and property history go with it. Whether the Agile web UI keeps a copy is not stated in the API docs, so do not count on one. Read the contact first if you need to keep anything.
Agile CRM: Delete Deal
PERMANENTLY delete a deal. Agile's REST documentation describes no trash, restore or undelete endpoint for deals, and answers 204 with an empty body, so nothing in this connector can bring it back - its notes and its links to contacts go with it. Agile does document an 'archived' flag on the deal object, so if you only want the deal out of the way, set archived through Update Deal instead of deleting it.
Agile CRM: Delete Event
PERMANENTLY delete a calendar event. Agile's REST documentation describes no trash, restore or undelete endpoint, and answers 204 with an empty body, so nothing in this connector can bring it back.
Agile CRM: Delete Note from Contact
Detach a note from a contact. Be precise about what this does: Agile describes it as removing the RELATIONSHIP between the note and the contact rather than as deleting the note record, and it answers 204 with an empty body. Either way it is not recoverable through this connector, because Agile publishes no endpoint that re-links an existing note to a contact - the only way back is to create a new note with the same text. Use Bulk Delete Notes to remove note records by id.
Agile CRM: Delete Task
PERMANENTLY delete a task. Agile's REST documentation describes no trash, restore or undelete endpoint for tasks, so nothing in this connector can bring it back. If what you want is to close the task rather than erase it, use Update Task with status COMPLETED instead - that keeps the history.
Agile CRM: Delete Track
PERMANENTLY delete a track. Agile documents no restore endpoint, so the track itself cannot be recovered through this connector - and it does not document what happens to the deals whose pipeline_id pointed at it, which is the more expensive unknown. Re-creating a track with the same name gives it a NEW id, so any deal still carrying the old id stays orphaned. Move the deals to another track first.
Agile CRM: Enroll Contact in Campaign
Add a contact to a marketing campaign, keyed on the contact's email address. This STARTS REAL OUTBOUND ACTIVITY - the campaign's emails and actions begin running against that contact - so it is reversible in the record-keeping sense (Remove Contact from Campaign unsubscribes them) but not in the sense that a sent email can be recalled. Sent form-encoded; the campaign id travels as the hyphenated key workflow-id, which this node handles for you.
Agile CRM: Remove Contact from Campaign
Unsubscribe a contact from a campaign, stopping any further campaign steps for them. Reversible - Enroll Contact in Campaign puts them back, though the campaign restarts rather than resuming. Nothing is deleted: neither the contact nor the campaign is affected beyond the subscription. Answers 204 with an empty body.
Agile CRM: Remove Contacts from Deal
Unlink specific contacts from a deal, leaving the deal's other contacts and every other field alone. This is the targeted counterpart to Update Deal, whose contact_ids replaces the whole list. Only the link is removed - no contact and no deal is deleted - and it is reversible by adding the ids back through Update Deal. Returns the updated deal.
Agile CRM: Remove Tags by Email
Find the contact with this exact email address and remove the named tags from it. Names that are not on the contact are ignored, and only the tag link is removed, never the contact. Reversible with Add Tags by Email. Sent form-encoded with the tag list serialized as JSON text. Answers 204 with no body.
Agile CRM: Remove Tags from Contact
Remove one or more tags from a contact or company by id. Agile matches each name against the record's tag list and removes the matches; names that are not present are ignored. Only the tag link is removed, never the contact. Reversible with Add Tags to Contact. Returns the remaining tag list.
Agile CRM: Set Contact Lead Score
SET a contact's lead score to an absolute value, by id. This replaces the score rather than adjusting it; use Adjust Contact Score by Email when you want to add or subtract. No other field on the contact is affected. Returns the updated contact.
Agile CRM: Update Company Properties
Partial update of a company's properties, on the same endpoint the contact update uses - this node exists so the id field asks for a company rather than a person. A MERGE: properties you do not name are left untouched, and no property can be deleted through it. Returns the updated company.
Agile CRM: Update Contact Properties
Partial update of a contact's properties. This is a MERGE, not a replace: properties you do not name are left untouched. Three limits are documented and matter. It CANNOT DELETE a property. It CANNOT change lead score, star value or tags (those have their own nodes). And where a multi-value SYSTEM field already has the subtype you send, the existing value is OVERWRITTEN rather than a second value being added, so sending phone/work replaces the work phone. Returns the updated contact.
Agile CRM: Update Deal
Partial update of a deal: fields you leave blank are not sent and are not changed. Two things behave as REPLACE rather than merge, and both bite. contact_ids REPLACES the deal's contact links with exactly the list you send, so sending one id unlinks the others - use Remove Contacts from Deal for a targeted removal. Sending a milestone in the wrong case is accepted but hides the deal from the milestone view. Returns the updated deal.
Agile CRM: Update Deal Note
Edit an existing deal note. The note id is mandatory; the endpoint is the same URL as the create, with PUT. Send deal_ids as well, because the documented request carries them on the update too. Contact notes have no equivalent - this asymmetry is Agile's, not the connector's.
Agile CRM: Update Event
Update a calendar event. Read the id warning before wiring this: Agile's docs state that without an id in the body the call is treated as a NEW EVENT, so a blank id field silently creates a duplicate instead of failing. The update goes to the same /events URL as the create, with PUT. Send the full event - title, start and end are mandatory here too.
Agile CRM: Update One Contact Property by Email
Add or overwrite ONE property on the contact with this email address. A POST that behaves as a partial update: it touches only the named property and leaves the rest of the contact alone. Note the documented hazard - Agile's docs state that if there is no matching contact it treats the call as a NEW CONTACT, so a blank or mistyped email address silently creates a record instead of failing. The email goes on the query string and the single property object is the JSON body. Returns the updated contact.
Agile CRM: Update Task
Partial update of a task: fields left blank are not sent and are not changed. This is also how a workflow closes a task - set status COMPLETED and is_complete true. One replace-not-merge trap: contacts REPLACES the task's related contacts with exactly the list you send. Returns the updated task.
Agile CRM: Update Track
Update a track's name or milestones. Read the id warning first: Agile's docs state that without an id in the body the call is treated as a NEW TRACK, so a blank id silently creates a duplicate track instead of failing. Renaming a milestone does not migrate the deals sitting in it - Agile matches deals to milestones by name, so a rename can orphan deals from the board view. Check the affected deals afterwards.
Connecting Agile CRM takes one credential
Agile CRM authenticates with HTTP Basic where the username is the account email of the user the key belongs to and the password is that user's REST API key. Every request also goes to your own subdomain, so three values are needed before a single call can be made: the domain, which is the first part of your Agile CRM web address, the email, and the key. The key is in Admin Settings under API and Analytics, where it is the first one, labelled as the API key for a REST client. The domain lives on the credential rather than on the nodes, because an Agile CRM key is minted inside one account and means nothing against any other subdomain, so one connection is one account and no node carries a domain field. That single choice removes a whole class of accident where half a workflow points at the wrong account. It also means the connection test cannot be a fixed address: Mattering builds it from your domain and calls the contacts list in its cheapest form, which proves the domain resolves, the base path is right, and the Basic header was built with the email as the username rather than the other way round. Worth knowing before you plan volume: Agile CRM publishes no rate limit in its REST documentation at all, no headers and no throttling section. The limit is a plan property instead, listed on the pricing page as a calls per day row.
Sign in to Agile CRM and note the subdomain in your address bar, which is the part before agilecrm.com.
Open Admin Settings, go to API and Analytics, and copy the first key listed, the one labelled for a REST client. It pairs with the email of whichever user you are signed in as.
In Mattering Automations, open Connectors, click Add Connector, choose Agile CRM, and create a credential with the domain, that email and the key.
Click Test Connection. Mattering asks your account for a single contact. An account with no contacts yet still passes, because an empty result proves the credential worked. A 401 means the email or the key is wrong, while a 404 means the domain is wrong and the request never reached an account at all.
All 60 Agile CRM nodes appear in the canvas palette. Run Agile CRM: List Tracks early: it returns your pipelines with their milestone names, which is the vocabulary the deal nodes match against.
Common uses for the Agile CRM MCP
Capture a lead once and score it every time it comes back
A form, an email or a row from another system arrives, and Agile CRM: Find Contact by Email checks whether the person is already known before anything is written. Agile CRM: Create Contact adds them if not, Agile CRM: Update Contact Properties merges new details onto an existing record, Agile CRM: Add Tags to Contact marks the segment, and Agile CRM: Set Contact Lead Score or Agile CRM: Adjust Contact Score by Email moves the score. That lookup is not optional politeness: Agile CRM has no duplicate check on contact creation, so a retried run without it makes a second record for the same person.
Keep the deal pipeline honest without anybody tidying it
Agile CRM: List Deals, Agile CRM: List Deals in Track and Agile CRM: List Deals Grouped by Milestone read the board, Agile CRM: Create Deal and Agile CRM: Update Deal write to it, and Agile CRM: List Tracks supplies the exact milestone spellings, which matters more than it sounds: Agile CRM matches milestone names case sensitively and accepts a wrong-case name without complaint, after which the deal is simply missing from the milestone view. A nightly sweep can find deals that have not moved, open a task on each one, and set the deal's archived flag rather than deleting anything.
Turn conversations elsewhere into CRM history
Agile CRM: Create Contact Note and Agile CRM: Create Deal Note write what happened into the record, Agile CRM: List Notes for Contact and Agile CRM: List Notes for Deal read it back, and Agile CRM: Create Event puts a meeting on the calendar. Because these are canvas nodes, the source can be anything else in the workflow: a call summary, a support ticket, a message in a channel, or an agent's own account of what it just did. One convention to build into templates is time: Agile CRM takes epoch seconds, not milliseconds, on due dates, close dates and event start and end times.
Follow-ups that get created and then get closed
Agile CRM: Create Task and Agile CRM: Create Task for Contact by Email open work, Agile CRM: List Tasks by Filter finds what is pending, and Agile CRM: Update Task moves it along. The softer alternative is worth naming here rather than in a footnote: closing a task by setting its status to completed keeps the history, while Agile CRM: Delete Task removes it with nothing in Agile CRM's documented API to bring it back.
Enroll people in campaigns from wherever the trigger really lives
Agile CRM: List Campaigns returns your campaigns, Agile CRM: Enroll Contact in Campaign puts a person into one by email, and Agile CRM: Remove Contact from Campaign takes them out. This is the one node family that reaches a real person under your name, so treat it accordingly: enrollment starts genuine outbound activity, and while removing someone stops future sends, nothing recalls an email that already went. Re-enrolling restarts the campaign rather than resuming it.
Export the CRM into whatever else needs it
Agile CRM: List Contacts, Agile CRM: List Companies, Agile CRM: Filter Contacts and Companies and Agile CRM: Search Contacts and Companies feed the rest of your stack: a Mattering database, a spreadsheet, a warehouse, or an agent that needs context before it answers. Two shapes are worth knowing before you wire a consumer. Names live inside a properties array rather than at the top level of a contact, so a first name is read out of that array rather than from a plain field. And paging is unusual: the total count is attached to the first record in the list and the cursor for the next page to the last one, rather than to any envelope, so a paging loop carries the cursor forward by hand.
Example: A demo request that becomes a scored contact, a deal and a task
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a form submission or a webhook from your site arrives in Mattering Automations with a name, an email and a company.
Agile CRM: Find Contact by Email looks the person up. Remember that a no-match here comes back as an empty success rather than an error, so the condition tests for content rather than for failure.
Where there is no match, Agile CRM: Create Contact writes the person with their properties and tags. Where there is one, Agile CRM: Update Contact Properties merges the new details onto the existing record without touching anything it did not send.
Agile CRM: Set Contact Lead Score raises the score for a demo request, and Agile CRM: Add Tags to Contact applies the campaign tag.
Agile CRM: List Tracks reads the pipeline so the next step uses a milestone name spelled exactly as Agile CRM has it, then Agile CRM: Create Deal opens the opportunity on that track with the contact attached.
Agile CRM: Create Task for Contact by Email opens the follow-up with an owner and a due date in epoch seconds, and a Mattering task opens for a human only if any step in the run failed.
Agile CRM MCP questions, answered
What Agile CRM operations are supported?
60 nodes: 23 read and 37 action. Contacts (list, get, create, update properties, set lead score, adjust score by email, add and remove tags by id or by email, change owner, update a single property by email, find by email, find by phone, search, dynamic filter, delete). Companies (list, create, get, update properties, delete). Deals (list, get, create, update, create for a contact by email, list by track, list grouped by milestone, list for a contact, remove contacts from a deal, delete, bulk delete). Tasks (list, list by filter, get, create, create for a contact by email, update, list for a contact, delete). Events (list, list for a contact, create, update, delete). Notes (create for a contact, create and update for a deal, list for a contact, list for a deal, delete from a contact, bulk delete). Campaigns (list, enroll a contact, remove a contact). Deliberately not built: the Documents API, which expects a file already hosted somewhere else, and the Help Desk ticketing surface, which is a separate product area with no reply, status or assignment endpoints documented.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Does Agile CRM publish an MCP server of its own?
We could not find one. Agile CRM's developer documentation is a REST reference and makes no mention of an MCP server, and nothing first-party turned up when this connector was researched. That is a statement about what we found rather than a promise about what the vendor will never ship, so it is worth re-checking if this matters to you. In the meantime this connector is how Agile CRM reaches an assistant: 60 nodes over MCP, and the same 60 nodes usable as steps on an automation canvas that runs on a schedule with nobody present.
Can I use this on the free plan, and what are the rate limits?
Agile CRM's REST documentation publishes no rate limit at all: no headers, no throttling section, and no 429 in any of its documented status lists. The limit is a plan property instead. Agile CRM's pricing page carries a calls per day row across its plan columns, and the lowest of those values is 500, which by position belongs to the free plan the page advertises as free for ten users with no card required. We would check that column alignment on the pricing page yourself before you design around the number, because the page renders its headers separately from the rows. What matters practically is the order of magnitude: a budget in the hundreds per day is small enough that a polling workflow on a five minute schedule spends most of it before doing any real work, so prefer event-driven runs and wider schedules, and batch reads where the API allows it.
Why does the credential ask for three things instead of a key?
Because Agile CRM needs three before it can answer a single call. Requests are HTTP Basic with your account email as the username and your REST API key as the password, and they go to your own subdomain, so the domain, the email and the key all have to be known. Only the key is secret. The domain sits on the credential rather than on the nodes because a key is minted inside exactly one account and is meaningless against another subdomain, which means one connection maps to one Agile CRM account, no node carries a domain field, and no workflow can end up pointing half its steps at the wrong account. The visible consequence is in the errors, and it is a useful one: a 401 means the email or the key is wrong, while a 404 from any node usually means the domain is wrong and the request never reached an account.
How do updates behave, and what is the create-on-missing-id trap?
Agile CRM documents no PATCH verb anywhere. Partial updates arrive as PUT on some paths and POST on others, and three different behaviours hide in that. Some merge, such as the contact properties update, which touches only the properties you name, cannot delete a property, and cannot change lead score, star value or tags, since each of those has its own endpoint. Some replace inside what looks like a partial update: the contact list on a deal and on a task is overwritten wholesale, so sending one id unlinks the rest, which is why removing a contact from a deal has its own targeted node. And four endpoints create a brand new record when the id is missing rather than failing, covering deals, events, tracks and the single-property contact update. That last one is the workflow breaker, because an empty template value does not error, it quietly makes a duplicate. Every affected node marks the id as required so the run stops before the request is sent, and says so in the field description.
Can an AI agent delete my CRM records?
Only if you let it, and nine nodes are flagged destructive so that is a decision rather than an accident: delete contact, delete company, delete deal, bulk delete deals, delete task, delete event, delete track, delete a note from a contact, and bulk delete notes. The honest scope of the warning is this: Agile CRM's REST documentation describes no trash, restore or undelete endpoint for any entity, so nothing deleted through this connector can be brought back through this connector. Whether the web interface keeps a copy is not something the API documentation says, so no claim is made either way. Two softer alternatives exist and the nodes name them: a deal has an archived flag you can set through the deal update instead of deleting it, and a task can be moved to completed status, which keeps the history. Deleting a track deserves extra thought, because Agile CRM does not document what happens to deals that pointed at it, and recreating a track with the same name produces a new id, so move deals off a track before removing it.
Why is there no contact picker on the nodes that take a contact id?
Because Agile CRM's payloads do not offer anything to label one with, and shipping a dropdown of bare numeric ids would be worse than a text box. A contact's first name, last name and email, and a company's name, live inside a properties array as name and value pairs rather than as top-level fields, and the path expressions that build pickers fan out over lists rather than selecting a list element by a sibling key. So the listers exist and return real ids, but every entry would be labelled with the id it is already showing. Pickers are declared where the vendor's payload supports them: deals by name with their milestone, tracks by name with their milestones, tasks by subject grouped by type, campaigns by name, and notes for a contact by subject, chained to the contact you already chose. The same shape is the reason a contact's name is read out of the properties array downstream rather than from a plain field.
Put Agile CRM to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Agile CRM is a product of its respective owner; Mattering is an independent platform.