Find work contact details and add people and companies to your own CRM from Claude, ChatGPT and other assistants. Checks for duplicates first and uses your field mapping and tags. Works with 29+ CRMs.
Handshake passed
- Endpoint
https://mcp.addtocrm.com/mcp- Category
- Finance & Payments
- Authentication
- other
- Maintainer
- Add to CRM
- Last checked
- 2026-11-02 22:08 UTC
Add the badge to your README
Verified means this server passed a live MCP handshake on 2026-11-02 22:08 UTC. The badge reflects the latest recorded check.
Markdown
[](https://appside.build/mcp-servers/add-to-crm/)HTML
<a href="https://appside.build/mcp-servers/add-to-crm/"><img src="https://appside.build/mcp-servers/add-to-crm/badge.svg" alt="Verified on Appside"></a>Connect with Claude Code
claude mcp add --transport http add-to-crm 'https://mcp.addtocrm.com/mcp'Connect with Cursor
Paste into .cursor/mcp.json.
{
"mcpServers": {
"add-to-crm": {
"url": "https://mcp.addtocrm.com/mcp"
}
}
}Complete the provider’s authentication flow in your client. For API keys, follow the maintainer’s instructions; never place secrets in a public listing.
Tools (18)
add_company_to_crmadd_people_to_crmadd_person_to_crmconfirm_possible_matchfind_company_detailsfind_contact_detailsfind_person_in_crmget_accountget_bulk_add_statusget_crm_recordget_profilelist_listslog_crm_activitysave_to_listsearch_companiessearch_crmsearch_prospectsupdate_crm_record
Submitted to mcpHQ/awesome-mcp-servers (PR #531) by philmcp. Public submission attribution does not establish ownership. Appside independently checks connectivity.
Your agent can submit and claim this for you
{"name":"create_account","arguments":{"agent":"My assistant","purpose":"mcp-directory"}}How we check servers
Each published entry passed a dated HTTPS Streamable HTTP check using the initialize-based MCP lifecycle (2024-11-05 through 2025-11-25): MCP initialize, followed by tools/list for open servers. For protected endpoints, a 401 response with an authentication challenge establishes reachability only. We never invoke tools. Failed checks stay in our source data and are excluded from the directory.
Checks are point-in-time observations, not continuous uptime monitoring. An authentication challenge does not prove tools are available. Appside does not endorse or audit listed servers. Review the maintainer’s permissions and policies before connecting.
What does the check verify?
We send an MCP initialize request over HTTPS. Open servers must return a valid tools/list response. Protected servers may qualify with an authentication challenge. A listing is not an endorsement or a security audit.
How can I update or remove a listing?
Sign in to a free Appside account, claim the listing with a token on its server or maintainer domain, then edit or remove it. You can also request removal at privacy@appside.build.