Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Beacon CRM MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read and filter Beacon CRM records of any type; create, update, upsert, delete records; run exports.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http beacon-crm-mcp-by-usefulapi https://beacon-crm.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# beaconcrm_list_record_types, beaconcrm_list_users, beaconcrm_list_records and 8 more
Beacon CRM MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http beacon-crm-mcp-by-usefulapi https://beacon-crm.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
List the users of the Beacon account (id, role, name, email). Use the inner user.id for 'link to a user' fields. GET /users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Results per page, 1-100 (default 25). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Results per page, 1-100 (default 25). |
| sort_by | string | no | Field key to sort by, e.g. created_at. |
| sort_direction | string | no | Sort direction (default: Beacon's default order). |
| populate | boolean | no | Include data from linked records (point-to-another-record fields). Beacon's default applies when omitted. |
| archived | boolean | no | true = list deleted (archived) records instead of active ones. |
One record by type and id, with all its fields. GET /entity/{entity}/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| id | integer | yes | Record id. |
| populate | boolean | no | Include data from linked records (point-to-another-record fields). Beacon's default applies when omitted. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| filter_conditions | array | yes | Filter conditions (see the description). An empty list matches every record. |
| filter_strictness | string | no | "all" = AND (default), "any" = OR. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Results per page, 1-100 (default 25). |
| sort_by | string | no | Field key to sort by, e.g. created_at. |
| sort_direction | string | no | Sort direction (default: Beacon's default order). |
| populate | boolean | no | Include data from linked records (point-to-another-record fields). Beacon's default applies when omitted. |
| archived | boolean | no | true = list deleted (archived) records instead of active ones. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| fields | object | 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]}); e |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| id | integer | yes | Record id. |
| fields | object | 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]}); e |
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 m
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| primary_field_key | string | yes | Field key used to match an existing record, e.g. emails or external_id. |
| fields | object | 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]}); e |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| id | integer | yes | Id of the record to delete. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_export_template_id | integer | yes | Id of the export template (shown in the Beacon URL when you view the template). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_export_id | no | Only this export (the id returned by beaconcrm_trigger_export). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Beacon CRM MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Beacon CRM MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.