Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
CRM 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.
84/100
tool-list score
30
tools declared
remote
at its publisher
—
calls last 7d
What it does
Your own CRM, fully customizable and agent-driven. Start with contacts, companies and a sales pipeli
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http crm-mcp https://api.mcp.ai/p_crm
# 2 — ask your agent for something these tools do
# crm_describe, crm_list_objects, crm_create_records and 27 more
CRM costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MDAll 1114 servers
mcp-dir1114 servers
18 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 crm-mcp https://api.mcp.ai/p_crmReconnect, 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
30 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.
Descreve o schema do CRM: todos os objetos (contact, company, deal e quaisquer custom) com seus campos (key, tipo, obrigatório, opções, relações) e o kanban. CHAME ISTO PRIMEIRO para saber quais objetos/campos existem antes de criar/ler registros.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | no | — |
Lista os objetos do CRM (key, rótulo, módulo, kanban). Versão enxuta do crm_describe, sem os campos.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | no | — |
Cria um registro (ou vários) de um objeto. Passe object (ex.: 'contact', 'deal') e data (objeto JSON com os campos por key). Para vários, use records (array JSON de {data}).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| data | string | no | — |
| metadata | string | no | — |
| records | string | no | — |
| account | string | no | — |
Lista registros de um objeto, com filtro/ordenação/paginação. filter é um objeto JSON: {campo: valor} ou {campo: {op: valor}} (ops: eq ne gt gte lt lte in nin contains exists).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| filter | string | no | — |
| sort | string | no | — |
| limit | number | no | — |
| offset | number | no | — |
| account | string | no | — |
Busca um ou mais registros de um objeto por id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| ids | array | yes | — |
| account | string | no | — |
Atualiza um registro (merge parcial) por id. Passe object, id e data (só os campos a mudar; null apaga o campo). Para vários, use updates (array JSON de {id, data}). Bulk support: accepts ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| id | string | no | — |
| data | string | no | — |
| metadata | string | no | — |
| updates | string | no | — |
| account | string | no | — |
| ids | array | no | — |
Remove um ou mais registros de um objeto por id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| ids | array | yes | — |
| account | string | no | — |
Busca textual nos registros (por nome/título/valores). Opcionalmente restrita a um object.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | — |
| object | string | no | — |
| limit | number | no | — |
| account | string | no | — |
Cria um OBJETO custom no CRM (além de contact/company/deal) e ganha CRUD/API automático. Passe key (api name, a-z/0-9/_), label e opcionalmente fields (array JSON de definições de campo).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | yes | — |
| label | string | no | — |
| module | string | no | — |
| display_field | string | no | — |
| fields | string | no | — |
| account | string | no | — |
Adiciona um CAMPO custom a um objeto (sem migração; registros antigos ficam sem a key). Tipos: string text integer float boolean date datetime singleselect multiselect email phone url currency relation user_ref json group.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| key | string | yes | — |
| label | string | no | — |
| type | string | yes | — |
| required | boolean | no | — |
| unique | boolean | no | — |
| indexed | boolean | no | — |
| options | string | no | — |
| relation | string | no | — |
| account | string | no | — |
Detalha UM objeto: seu rótulo, kanban e todos os campos (key, tipo, obrigatório, opções, relação). Versão focada do crm_describe.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| account | string | no | — |
Edita um objeto: rótulo, campo de exibição, módulo ou config de kanban (a key é imutável). Vale para objetos de sistema e custom.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| label | string | no | — |
| display_field | string | no | — |
| module | string | no | — |
| kanban | string | no | — |
| account | string | no | — |
Remove um objeto CUSTOM (objetos de sistema não podem ser removidos). Se houver registros, passe delete_records:true para apagar tudo junto.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| delete_records | boolean | no | — |
| account | string | no | — |
Edita um campo: rótulo, obrigatório, visível, posição, opções, indexação. Mudança de TIPO só é permitida se for um alargamento seguro (ex.: integer→float); mudança com perda é bloqueada (crie um campo novo e migre).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| key | string | yes | — |
| type | string | no | — |
| label | string | no | — |
| required | boolean | no | — |
| visible | boolean | no | — |
| position | number | no | — |
| indexed | boolean | no | — |
| options | string | no | — |
| account | string | no | — |
Remove um campo CUSTOM (soft-delete: some do schema, mas os valores já gravados ficam preservados). Campos de sistema não podem ser removidos.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| key | string | yes | — |
| account | string | no | — |
Liga um registro a outro por um campo de relação (ex.: vincular um contato a uma empresa). Para relação 'many' adiciona ao conjunto; para 'single' define o alvo. Bulk support: accepts ids, target_ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| id | string | yes | — |
| field | string | yes | — |
| target_id | string | yes | — |
| account | string | no | — |
| ids | array | no | — |
| target_ids | array | no | — |
Desfaz uma relação. Para relação 'many' remove o target_id do conjunto; para 'single' limpa o campo (target_id opcional). Bulk support: accepts ids, target_ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| id | string | yes | — |
| field | string | yes | — |
| target_id | string | no | — |
| account | string | no | — |
| ids | array | no | — |
| target_ids | array | no | — |
Resolve os registros relacionados de um registro: segue os campos de relação e devolve os registros-alvo (todos, ou só de um field). Bulk support: accepts ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| id | string | yes | — |
| field | string | no | — |
| account | string | no | — |
| ids | array | no | — |
Move um registro de um objeto kanban (ex.: deal) para outra etapa do funil. Valida a etapa contra as opções do campo de stage. Bulk support: accepts ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | yes | — |
| id | string | yes | — |
| stage | string | yes | — |
| account | string | no | — |
| ids | array | no | — |
Inicia o upload de um arquivo (até 200 MB) e devolve uma URL presigned (upload_url) pra fazer o PUT direto no storage, mais o file_id. Depois do PUT, chame crm_confirm_upload. Opcional: anexe a um registro com object+record_id. Bulk support: accepts record_ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filename | string | yes | — |
| size | number | yes | — |
| content_type | string | no | — |
| object | string | no | — |
| record_id | string | no | — |
| account | string | no | — |
| record_ids | array | no | — |
Confirma o upload depois do PUT na upload_url (o storage valida o tamanho real). Marca o arquivo como pronto e contabiliza no uso. Bulk support: accepts file_ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_id | string | yes | — |
| account | string | no | — |
| file_ids | array | no | — |
Sobe um arquivo A PARTIR DE UMA URL (a plataforma baixa e armazena, até 200 MB) — o jeito do AGENTE subir via API sem segurar os bytes. Devolve o arquivo já pronto. Opcional: anexe a um registro com object+record_id. Bulk support: accepts record_ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | — |
| filename | string | no | — |
| content_type | string | no | — |
| object | string | no | — |
| record_id | string | no | — |
| account | string | no | — |
| record_ids | array | no | — |
Lista os arquivos do CRM (id, nome, tamanho, status). Opcionalmente filtra os anexados a um objeto/registro. Bulk support: accepts record_ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object | string | no | — |
| record_id | string | no | — |
| account | string | no | — |
| record_ids | array | no | — |
Metadados de um arquivo (nome, tamanho, content_type, status, anexo). Bulk support: accepts file_ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_id | string | yes | — |
| account | string | no | — |
| file_ids | array | no | — |
Gera uma URL presigned de download (GET) pra um arquivo. A URL expira em alguns minutos. Bulk support: accepts file_ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_id | string | yes | — |
| account | string | no | — |
| file_ids | array | no | — |
Remove um ou mais arquivos (apaga do storage e libera o espaço contabilizado).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | no | — |
| file_id | string | no | — |
| account | string | no | — |
Torna um arquivo PÚBLICO e devolve uma URL estável (https://api.mcp.ai/f/<token>) pra embutir num site (ex.: thumbnail). O objeto continua privado no storage, o token é a chave (revogável com crm_unpublish_file). Egress da visualização pública é contabilizado. Bulk support: accepts file_ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_id | string | yes | — |
| account | string | no | — |
| file_ids | array | no | — |
Revoga o link público de um arquivo (o token para de funcionar na hora). Bulk support: accepts file_ids for batched execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_id | string | yes | — |
| account | string | no | — |
| file_ids | array | no | — |
Uso de storage deste CRM: bytes do banco + bytes de arquivos, total em GB, nº de arquivos e egress acumulado. É a base do que é cobrado (storage GB-mês + egress).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | no | — |
Lista os CRMs conectados neste install. Retorna cada um com id, rótulo e is_default (true quando só há um, não precisa passar account nas outras tools).
No parameter schema on file.
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 CRM 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: —
BTool-list grade · score 84 / 100
Release 0.1.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score94
Client score84
Findings1 threat · 3 capability
Capabilityhigh
Coveragemanifest
Verificationnot in this report
Surface digestf87555f4a699b1d89e3e51b260848ee02055cb01f50093e5e43922e2c57ad9f1
Score vectorthreat 94 → client 84
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| crm_describe | no tags | |
| crm_list_objects | no tags | |
| crm_create_records | state-write | state-write: declares readOnlyHint: false |
| crm_list_records | no tags | |
| crm_get_records | no tags | |
| crm_update_records | state-write | state-write: declares readOnlyHint: false |
| crm_delete_records | state-write | state-write: declares readOnlyHint: false |
| crm_search | no tags | |
| crm_define_object | state-write | state-write: declares readOnlyHint: false |
| crm_add_field | state-write | state-write: declares readOnlyHint: false |
| crm_get_object | no tags | |
| crm_update_object | state-write | state-write: declares readOnlyHint: false |
| crm_delete_object | state-write | state-write: declares readOnlyHint: false |
| crm_update_field | state-write | state-write: declares readOnlyHint: false |
| crm_remove_field | state-write | state-write: declares readOnlyHint: false |
| crm_link_record | state-write | state-write: declares readOnlyHint: false |
| crm_unlink_record | state-write | state-write: declares readOnlyHint: false |
| crm_related_records | no tags | |
| crm_move_stage | state-write | state-write: declares readOnlyHint: false |
| crm_upload_file | external-sinkstate-write | external-sink: keyword "upload_file"; state-write: declares readOnlyHint: false |
| crm_confirm_upload | state-write | state-write: declares readOnlyHint: false |
| crm_upload_from_url | state-write | state-write: declares readOnlyHint: false |
| crm_list_files | sensitive-source | sensitive-source: keyword "list_files" |
| crm_get_file | no tags | |
| crm_download_file | untrusted-input | untrusted-input: keyword "download" |
| crm_delete_file | file-writestate-write | file-write: keyword "delete_file" in tool name; state-write: declares readOnlyHint: false |
| crm_publish_file | state-write | state-write: declares readOnlyHint: false |
| crm_unpublish_file | state-write | state-write: declares readOnlyHint: false |
| crm_usage | no tags | |
| crm_list_accounts | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
crm_download_file → crm_list_files → crm_upload_file
A cross-tool exfiltration chain exists: crm_download_file → crm_list_files → crm_upload_file.
Supply chain and provenance
Integrityfirst-seen
Surface digestf87555f4a699b1d8
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 0.1.0.
0.1.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 CRM 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.