Read and filter Beacon CRM records of any type; create, update, upsert, delete records; run exports. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"beacon-crm": {
"url": "https://beacon-crm.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"beacon-crm": {
"type": "http",
"url": "https://beacon-crm.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Beacon account id and Beacon API key.
Create the key in Beacon → Settings → API keys → Create API key (admins only; the API needs the Standard, Premium or Ultimate plan). The key is shown once. The account id is the number in the Beacon address bar after you log in. The key acts with your account's access, so changes it makes are real changes to your database. Your key is used only to call the Beacon API on your behalf; it is never shown to anyone.
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: the login page asks for your Beacon account id and Beacon API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
beaconcrm_list_record_types | read | 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. |
beaconcrm_list_users | read | 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. |
beaconcrm_list_records | read | List 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}. |
beaconcrm_get_record | read | Get record One record by type and id, with all its fields. GET /entity/{entity}/{id}. |
beaconcrm_filter_records | read | Filter 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. |
beaconcrm_create_record | write | Create 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}. |
beaconcrm_update_record | write | Update 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}. |
beaconcrm_upsert_record | write | Create 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. |
beaconcrm_delete_record | write | Delete 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}. |
beaconcrm_trigger_export | write | Start 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. |
beaconcrm_list_exports | read | List 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. |
beaconcrm_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
beaconcrm_request_feature | Request a missing feature Tell usefulapi that the user needs something the Beacon CRM tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
beaconcrm_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Beacon CRM tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
beaconcrm_cancel_subscription | Cancel the Pro subscription Cancel the caller's Beacon CRM Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run beaconcrm_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited |
Pro covers this Beacon CRM 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].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Beacon CRM. The server calls the Beacon CRM API with your own Beacon CRM access, so it sees only the data that your account can see.
The login page asks for your Beacon account id and Beacon API key. See Before you connect for where to find them.
No. 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: the login page asks for your Beacon account id and Beacon API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Beacon CRM API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Beacon CRM.
Yes, if you approve it. 5 of the 11 Beacon CRM tools can create or change data. The other 6 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Beacon CRM server only. Run beaconcrm_usage_status to see how many calls you used.
Ask the AI to run beaconcrm_upgrade: it returns a Stripe Checkout link. To cancel, run beaconcrm_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with beaconcrm_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.