Read and filter Beacon CRM records of any type; create, update, upsert, delete records; run exports.
Score is being calculated.
WRITE: create ONE new record of the given type in the live Beacon database. Not idempotent: calling it twice creates two records (use beaconcrm_upsert_record to avoid duplicates). Beacon workflows may run as a result. Invalid field values are rejected with the rule that failed. POST /entity/{entity}.
| Name | Required | Description | Default |
|---|---|---|---|
| entity | Yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. | |
| fields | Yes | Field values keyed by field key, in Beacon's field formats (see beaconcrm_list_record_types for keys). Select and point-to-record fields are ARRAYS (e.g. {"type": ["Donation"], "customer": [1725]}); emails are [{"email", "is_primary"}]; currency is {"value", "currency"}; dates are ISO strings. |
WRITE, DESTRUCTIVE: delete ONE record. Beacon keeps deleted records as 'archived' (listable with archived=true), but this server has no restore tool, so treat the deletion as irreversible. Related data that depends on the record may be affected. It is sent once and never retried. DELETE /entity/{entity}/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Id of the record to delete. | |
| entity | Yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
Search records of one type with Beacon filter conditions (read-only; it uses POST because the filter is a body). Each condition is {"field", "operator", "value"}. Operators by field type: text == != starts_with ends_with contains not_contains null not_null; select (value is an array) contains not_contains in not_in null not_null; number == != > < null not_null; date date_on date_after date_before date_between (value e.g. "2026-01-01", "last_month", or ["2026-01-01","2026-06-01"]); checkbox == true; point-to-record (value is an array of ids) contains not_contains. Location parts: address.city etc.; emails: emails.email. Conditions can nest as {"filter_conditions": [...], "filter_strictness": "all"|"any"}. Example: [{"field":"emails.email","operator":"==","value":"a@b.org"}]. POST /entities/{entity}/filter.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, from 1 (default 1). Pass the previous reply's next_page. | |
| entity | Yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. | |
| sort_by | No | Field key to sort by, e.g. created_at. | |
| archived | No | true = list deleted (archived) records instead of active ones. | |
| per_page | No | Results per page, 1-100 (default 25). | |
| populate | No | Include data from linked records (point-to-another-record fields). Beacon's default applies when omitted. | |
| sort_direction | No | Sort direction (default: Beacon's default order). | |
| filter_conditions | Yes | Filter conditions (see the description). An empty list matches every record. | |
| filter_strictness | No | "all" = AND (default), "any" = OR. |
One record by type and id, with all its fields. GET /entity/{entity}/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Record id. | |
| entity | Yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. | |
| populate | No | Include data from linked records (point-to-another-record fields). Beacon's default applies when omitted. |
List recent export jobs with status, progress (100 = complete) and, when complete, a signed download url. Pass entity_export_id to check one job started by beaconcrm_trigger_export. GET /entity_exports.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_export_id | No | Only this export (the id returned by beaconcrm_trigger_export). |
List records of one type (for example person, organization, payment), one page at a time. Use beaconcrm_filter_records to search by field values. GET /entities/{entity}.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, from 1 (default 1). Pass the previous reply's next_page. | |
| entity | Yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. | |
| sort_by | No | Field key to sort by, e.g. created_at. | |
| archived | No | true = list deleted (archived) records instead of active ones. | |
| per_page | No | Results per page, 1-100 (default 25). | |
| populate | No | Include data from linked records (point-to-another-record fields). Beacon's default applies when omitted. | |
| sort_direction | No | Sort direction (default: Beacon's default order). |
List the record types of this Beacon account (people, organisations, payments, custom types, ...) with their fields (keys, types, options). Call this first: the keys are what the other tools take as entity and as field names. GET /entity_types.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
List the users of the Beacon account (id, role, name, email). Use the inner user.id for 'link to a user' fields. GET /users.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, from 1 (default 1). Pass the previous reply's next_page. | |
| per_page | No | Results per page, 1-100 (default 25). |
WRITE: start an export job from an existing export template (created in Beacon). Returns the new export's id with status in_progress; then poll beaconcrm_list_exports with that id until progress is 100 and it carries a download url. Each call starts another job. POST /entity_export/trigger.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_export_template_id | Yes | Id of the export template (shown in the Beacon URL when you view the template). |
WRITE: change fields of ONE existing record. Only the fields you pass are changed; a select or reference field passed as an empty array [] is CLEARED, removing its existing values. The previous values are not kept by this tool. Beacon workflows may run as a result. PATCH /entity/{entity}/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Record id. | |
| entity | Yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. | |
| fields | Yes | Field values keyed by field key, in Beacon's field formats (see beaconcrm_list_record_types for keys). Select and point-to-record fields are ARRAYS (e.g. {"type": ["Donation"], "customer": [1725]}); emails are [{"email", "is_primary"}]; currency is {"value", "currency"}; dates are ISO strings. |
WRITE: create a record, or update the existing one whose key field matches. primary_field_key names the field used to find the match (for example "emails" for a person, or "external_id"); fields must contain a value for it. If a record matches it is UPDATED with the given fields (an empty array leaves an existing value untouched on upsert); otherwise a new record is created. Beacon workflows may run as a result. PUT /entity/{entity}/upsert.
| Name | Required | Description | Default |
|---|---|---|---|
| entity | Yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. | |
| fields | Yes | Field values keyed by field key, in Beacon's field formats (see beaconcrm_list_record_types for keys). Select and point-to-record fields are ARRAYS (e.g. {"type": ["Donation"], "customer": [1725]}); emails are [{"email", "is_primary"}]; currency is {"value", "currency"}; dates are ISO strings. | |
| primary_field_key | Yes | Field key used to match an existing record, e.g. emails or external_id. |
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
beaconcrm_create_recordbeaconcrm_delete_recordbeaconcrm_filter_recordsbeaconcrm_get_recordbeaconcrm_list_exportsbeaconcrm_list_record_typesbeaconcrm_list_recordsbeaconcrm_list_usersbeaconcrm_trigger_exportbeaconcrm_update_recordbeaconcrm_upsert_recordRead people, companies, opportunities, notes and tasks; create and update records in Twenty CRM.
Read deals, persons, organizations, activities and pipelines; create and update CRM records.
Read campaigns, donations, profiles and supporters; record offline donations and upsert users.
Read, create, update and delete records; inspect objects, fields and schema in your Knack database.
Add one secure layer between your agents and this server.