Beacon CRM MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.3.3 · published by io.usefulapi

Read and filter Beacon CRM records of any type; create, update, upsert, delete records; run exports.

Deletes · 3Changes · 2

Compare Registry entry

11 tools: 3 can delete or cancel things, 2 change things and 6 only read.

Scanned Oct 21, 2026

Deletes or cancels3Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things2Claude Code: ask: see these tools
Only reads6Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http beacon-crm https://beacon-crm.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

11 tools

Deletes or cancels 3Removes, cancels or revokes something.Claude Code: deny

beaconcrm_delete_recordWRITE, DESTRUCTIVE: delete ONE record.No findings
Why it is in this group
- The name "beaconcrm_delete_record" says "delete": a word for removing or ending something.
- The description says "irreversible".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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}.
Annotations the server declares
- title: Delete record
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
beaconcrm_update_recordWRITE: change fields of ONE existing record.No findings
Why it is in this group
- The name "beaconcrm_update_record" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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}.
Annotations the server declares
- title: Update record
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
beaconcrm_upsert_recordWRITE: create a record, or update the existing one whose key field matches.No findings
Why it is in this group
- The name "beaconcrm_upsert_record" says "upsert": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Create or update record by key field
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true

Changes things 2Creates or changes something that can be changed back.Claude Code: ask

beaconcrm_create_recordWRITE: create ONE new record of the given type in the live Beacon database.No findings
Why it is in this group
- The name "beaconcrm_create_record" says "create": a word for a change.
Description, as the server wrote it
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}.
Annotations the server declares
- title: Create record
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
beaconcrm_trigger_exportWRITE: start an export job from an existing export template (created in Beacon).No findings
Why it is in this group
- The name "beaconcrm_trigger_export" says "trigger": a word for a change.
Description, as the server wrote it
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.
Annotations the server declares
- title: Start an export
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true

Only reads 6Looks things up and changes nothing.Claude Code: allow

beaconcrm_filter_recordsSearch records of one type with Beacon filter conditions (read-only; it uses POST because the filter is a body).No findings
Why it is in this group
- The description's first verb is "search": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: Filter records
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
beaconcrm_get_recordOne record by type and id, with all its fields.No findings
Why it is in this group
- The name "beaconcrm_get_record" says "get": a word for reading.
Description, as the server wrote it
One record by type and id, with all its fields. GET /entity/{entity}/{id}.
Annotations the server declares
- title: Get record
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
beaconcrm_list_exportsList recent export jobs with status, progress (100 = complete) and, when complete, a signed download url.No findings
Why it is in this group
- The name "beaconcrm_list_exports" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List exports
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
beaconcrm_list_record_typesList the record types of this Beacon account (people, organisations, payments, custom types, ...) with their fields (keys, types, options).No findings
Why it is in this group
- The name "beaconcrm_list_record_types" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List record types and fields
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
beaconcrm_list_recordsList records of one type (for example person, organization, payment), one page at a time.No findings
Why it is in this group
- The name "beaconcrm_list_records" says "list": a word for reading.
Description, as the server wrote it
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}.
Annotations the server declares
- title: List records
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
beaconcrm_list_usersList the users of the Beacon account (id, role, name, email).No findings
Why it is in this group
- The name "beaconcrm_list_users" says "list": a word for reading.
Description, as the server wrote it
List the users of the Beacon account (id, role, name, email). Use the inner user.id for 'link to a user' fields. GET /users.
Annotations the server declares
- title: List account users
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.3.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http beacon-crm https://beacon-crm.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__beacon-crm__beaconcrm_list_record_types",
      "mcp__beacon-crm__beaconcrm_list_users",
      "mcp__beacon-crm__beaconcrm_list_records",
      "mcp__beacon-crm__beaconcrm_get_record",
      "mcp__beacon-crm__beaconcrm_filter_records",
      "mcp__beacon-crm__beaconcrm_list_exports"
    ],
    "ask": [
      "mcp__beacon-crm__beaconcrm_create_record",
      "mcp__beacon-crm__beaconcrm_trigger_export"
    ],
    "deny": [
      "mcp__beacon-crm__beaconcrm_update_record",
      "mcp__beacon-crm__beaconcrm_upsert_record",
      "mcp__beacon-crm__beaconcrm_delete_record"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as beacon-crm. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/beacon-crm/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing