io.usefulapiPublished by usefulapi.ioOfficial publisherv1.23.5Updated Nov 8, 2026
Read and filter Beacon CRM records of any type; create, update, upsert, delete records; run exports.
The publisher's own server: Ably MCP by usefulapi
Beacon CRM MCP by usefulapi's hosted MCP server (beacon-crm.usefulapi.io), published by usefulapi.io; no sign-in required; Streamable HTTP; 11 tools.
No AI overview yet: these facts come from the registry entry and the server itself.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.usefulapi%2Fbeacon-crm/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"beacon-crm-by-usefulapi": {
"type": "http",
"url": "https://beacon-crm.usefulapi.io/mcp"
}
}
}Use Beacon CRM from Claude, Cursor, or any MCP client — record types and users, list, get and filter records of any type (people, organisations, payments, and your custom types), create, update, upsert and delete records, and trigger and list exports. Hosted, no local install: connect with your own Beacon CRM credentials.
Live endpoint: https://beacon-crm.usefulapi.io/mcp · Homepage: https://usefulapi.io/beacon-crm
https://beacon-crm.usefulapi.io/mcp.claude mcp add --transport http beacon-crm https://beacon-crm.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Beacon CRM credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/beacon-crm/
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with beaconcrm_upgrade (it returns a Stripe Checkout link). Cancel any time with beaconcrm_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running beaconcrm_upgrade before then undoes the cancel. Or write to [email protected].
MIT © usefulapi. Not affiliated with or endorsed by Beacon CRM.
Source: servers/beacon-crm/README.md at commit 4046075
List record types and fields
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.
Takes no parameters.
List account users
List the users of the Beacon account (id, role, name, email). Use the inner user.id for 'link to a user' fields. GET /users.
pageper_pageList records
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}.
pageentityrequiredsort_byarchivedper_pagepopulatesort_directionGet record
One record by type and id, with all its fields. GET /entity/{entity}/{id}.
idrequiredentityrequiredpopulateFilter records
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":"[email protected]"}]. POST /entities/{entity}/filter.
pageentityrequiredsort_byarchivedper_pagepopulatesort_directionfilter_conditionsrequiredfilter_strictnessCreate record
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}.
entityrequiredfieldsrequiredUpdate record
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}.
idrequiredentityrequiredfieldsrequiredCreate or update record by key field
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.
entityrequiredfieldsrequiredprimary_field_keyrequiredDelete record
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}.
idrequiredentityrequiredStart an export
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.
entity_export_template_idrequiredList exports
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.
entity_export_id100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
io.usefulapiOfficial publisher
Ably MCP by usefulapi's hosted MCP server, published by usefulapi.io; no sign-in required; Streamable HTTP; 15 tools.
io.usefulapiOfficial publisher
Hosted read-only MCP server that lets an assistant read Tiltify campaigns, donations and top donor and fundraiser leaderboards.
io.usefulapiOfficial publisher
Hosted Termii server that lets an assistant send SMS, check wallet balance, DND status, sender IDs and message history.
io.usefulapiOfficial publisher
Hosted MCP server that lets an assistant read Temp Stick temperature and humidity sensors, their readings and alert notifications.
io.usefulapiOfficial publisher
Connects an assistant to a Stibee email marketing workspace to read address books, subscribers and email stats, and to add subscribers and group members.
{ "mcpServers": { "beacon-crm": { "url": "https://beacon-crm.usefulapi.io/mcp" } }}