Most AI tools are reactive. You open them, type a question, get an answer, close them. Hermes Agent is different. It runs on your server 24/7, lives in your Telegram or Discord, learns from every interaction, and gets more capable the longer it operates. It is less of a tool and more of a teammate that happens to never sleep.

But here is the problem most people hit immediately: Hermes is only as useful as the data you give it access to. If you wire it to a CRM that surfaces contacts, emails and not much else, Hermes can book you a call or update a field. If you connect it to a CRM that gives it your full conversation history across email, LinkedIn, WhatsApp and Telegram, Hermes can reason about deals the same way a senior account executive would, across every channel simultaneously, at 2am, without you touching a keyboard.

The five CRMs below are the ones with real MCP servers you can add to ~/.hermes/config.yaml today. I ranked them by how much context they actually give Hermes to work with.

The channels each CRM exposes to Hermes via MCP. Hermes lives in Telegram, Discord, WhatsApp and Slack — the CRM that mirrors those channels gives it the richest sales context.

TL;DR: The 5 CRMs With a Real MCP Server for Hermes Agent 🏆

• 🏆 Breakcold: Tier 1 native in Hermes' official client list. 55 tools. The only CRM whose MCP gives Hermes access to LinkedIn DMs, WhatsApp, Telegram and email alongside records, tasks and meetings. Full context in one connection.

• 🟠 HubSpot: Official MCP at mcp.hubspot.com. Deepest CRM-object coverage of the group. Email, calls, meetings in scope. No IM channels.

• ⚫ Attio: Official MCP at mcp.attio.com/mcp. Excellent relational data model, real meeting transcripts via MCP. No IM channels.

• 🔵 Salesforce: Hosted MCP per org. The enterprise pick. Powerful but needs an admin to configure and gives Hermes no visibility into IM conversations.

• 🟢 Close: Official MCP at mcp.close.com/mcp. The cleanest auth model of the group (three scope tiers). Best for phone-heavy teams.

How Hermes Agent connects to a CRM 🔌

Hermes uses Model Context Protocol as its primary integration layer. Every MCP server you configure in ~/.hermes/config.yaml becomes a set of tools Hermes can invoke autonomously. The agent discovers tools at startup (and on config reload), registers them with a mcp_<server_name>_<tool_name> prefix, and starts calling them without you doing anything further.

The config format is straightforward. For HTTP-based MCP servers (which is how all five CRMs below work), it looks like this:

mcp_servers:
  your_crm:
    url: "https://mcp.yourcrm.com/v1"
    headers:
      Authorization: "Bearer your_api_key"

That is it. Hermes does the rest: discovers available tools, loads them, and you can ask it from Telegram "what are my open deals this week" and it will call the CRM directly. The best practice from the Hermes docs is to use an include allowlist on sensitive servers — start with read tools only, add writes when you trust the agent's judgment on that CRM.

1. Breakcold: The CRM Built for the Same World Hermes Lives In 🏆

Full disclosure: I co-founded Breakcold. Every technical claim is verifiable against our public docs.

Breakcold officially supports Hermes Agent in Tier 1 of its AI client list, alongside Claude, Claude Code and Codex CLI. That is Breakcold's own tier diagram — meaning Breakcold ships a native AgentSkill so Hermes can connect with no manual MCP config required. Hermes Agent operates through Telegram, Discord, WhatsApp, Slack and Signal. Breakcold natively integrates email, LinkedIn, WhatsApp, Telegram, calls and meetings. That overlap is not a coincidence. Hermes is designed to live in your messaging channels. Breakcold is designed to be your CRM inside those same channels. They are solving the same problem from opposite directions.

Breakcold's official 17-client support tier diagram. Hermes Agent sits in Tier 1 alongside Claude and Codex CLI, meaning Breakcold ships a native AgentSkill for Hermes — the only CRM to do so.

The specific capability that makes this combination powerful: Breakcold's MCP exposes multi-channel conversation history through a single inbox endpoint. When you ask Hermes "what did we talk about with this prospect last week," it calls inbox_conversations_list and gets back LinkedIn DM threads, WhatsApp conversations and Telegram messages alongside email. No other CRM on this list gives Hermes that view. Every other one stops at email.

Config 🛠️

mcp_servers:
  breakcold:
    url: "https://http.us.breakcold.com/mcp/v1"  # or .eu for European region
    headers:
      Authorization: "Bearer bc_live_..."
    tools:
      include:
        - records_list
        - records_get
        - records_update
        - inbox_conversations_list
        - inbox_messages_list
        - tasks_list
        - tasks_create
        - notes_create

What you can ask Hermes from Telegram 💬

• "What deals have gone quiet on LinkedIn this week?" — Hermes reads inbox threads, spots no-reply signals, surfaces the list.

• "Update the pipeline stage for Acme to Proposal Sent." — Hermes calls records_update, done in two seconds.

• "Write a note on the TechCorp deal summarizing our last three conversations." — Hermes pulls LinkedIn + WhatsApp + email threads, synthesizes, calls notes_create.

• "Create a follow-up task for every deal that hasn't moved in 10 days." — Hermes lists deals, filters by last activity, batch-creates tasks with tasks_create.

• "Who among my prospects replied on Telegram but I haven't responded to?" — Hermes scans the Telegram channel in the inbox, flags unanswered threads.

55 MCP tools generated from the same OpenAPI contract as Breakcold's public REST API. US endpoint: https://http.us.breakcold.com/mcp/v1. EU: https://http.eu.breakcold.com/mcp/v1. OAuth and Bearer token both supported. Scoped: records:read/write, tasks:read/write, notes:read/write, inbox:read.

Pricing: $59/mo flat. Add a seat for $10. A 5-person team costs $99/mo total. That is less than one seat on most competing products.

Claude (via Breakcold MCP) stepping through a deal stage analysis, reading LinkedIn and Telegram conversation history alongside email to assess pipeline position. Hermes Agent does the same reasoning, but autonomously and from your messaging app.

Start your 14-day Breakcold trial → · MCP documentation

2. HubSpot: The Deepest CRM-Object Coverage 🟠

HubSpot ships a real hosted MCP server at mcp.hubspot.com with OAuth 2.0 auth. The object coverage is the widest of the group: contacts, companies, deals, tickets, products, line items, invoices, quotes, orders, segments. On the activity side you get calls, emails, meetings, notes and tasks. You also get organizational context (users, teams, owners) and marketing data (campaigns, blog posts, landing pages) read-only.

When you ask Hermes "give me all open deals in the Negotiation stage with their contact last activity date," HubSpot's MCP can return that. The breadth of objects is genuinely impressive. The limitation is on the conversation side: HubSpot's MCP stops at email. No LinkedIn DMs, no WhatsApp, no Telegram. So Hermes' view of your relationships is bounded by what happened in Gmail or Outlook.

For inbound SaaS teams running email-centric sales, this is a solid combination. For outbound teams selling over multiple channels, it is a partial picture.

Config 🛠️

mcp_servers:
  hubspot:
    url: "https://mcp.hubspot.com"
    # Auth via OAuth 2.0 — set up in HubSpot developer portal
    # Create a Private App, grant CRM read/write scopes, use the token

Docs: developers.hubspot.com/docs/apps/developer-platform

3. Attio: Best Data Model, Real Meeting Transcripts ⚫

Attio runs a solid MCP server at mcp.attio.com/mcp. The relational data model is Attio's main strength and it carries through to the MCP: you can query across people, companies, deals, notes, tasks, comments and lists. Importantly, Attio exposes meeting recordings and transcripts via MCP, which makes it one of the better options for teams who want Hermes to reason over actual call content, not just metadata.

Attio positions itself as the next Salesforce for ops-heavy technical teams. That profile shows in the MCP: the tools are powerful and the data model is flexible. No IM channels in scope — no LinkedIn, WhatsApp or Telegram. If your deals close over phone calls and emails and your team enjoys building custom workflows on a relational CRM, Attio plus Hermes is a good pairing.

Config 🛠️

mcp_servers:
  attio:
    url: "https://mcp.attio.com/mcp"
    headers:
      Authorization: "Bearer your_attio_api_key"
    tools:
      include:
        - list_records
        - get_record
        - update_record
        - list_notes
        - create_note
        - list_tasks
        - list_meetings

Docs: docs.attio.com/mcp/overview

4. Salesforce: Enterprise MCP With Full SObject Access 🔵

Salesforce ships a Hosted MCP product that exposes SObject operations with field-level security enforced, Apex Invocable Actions, Flows, Data 360 SQL queries and Tableau analytics. Each org gets its own MCP endpoint configured by an admin. Auth is per-user OAuth 2.0 with PKCE.

The power is real. Hermes can query SObjects in natural language, run Apex flows by name, fetch pipeline analytics from Tableau. If you are at enterprise scale with a Salesforce admin and you want Hermes to operate your CRM with proper governance, this works. The barrier is setup overhead: there is no "paste this URL into your config" path. Your Salesforce admin configures the MCP endpoint, manages trust settings and scopes. For a 5-person startup, that is a lot. For a 200-person company already running Salesforce, it is just another config step.

No LinkedIn, WhatsApp or Telegram via MCP, which is expected. Salesforce's domain is core enterprise SFA.

Config 🛠️

mcp_servers:
  salesforce:
    url: "https://your-org.my.salesforce.com/services/mcp/v1"
    # OAuth 2.0 + PKCE — configured by your Salesforce admin
    # Each user authenticates against their own org endpoint

Docs: developer.salesforce.com/docs/platform/hosted-mcp-servers/guide

5. Close: Cleanest MCP Auth Model, Phone-First 🟢

Close runs an MCP server at mcp.close.com/mcp with Streamable HTTP transport and one of the most sensible auth models in this list. Three permission tiers: read, write_safe, write_destructive. You give Hermes the smallest scope it needs, nothing wider. For a read-only briefing agent you grant read only. When you trust it to update fields, add write_safe. Never give write_destructive to an autonomous agent.

Close's strength is calling. If your team is phone-heavy, Hermes connected to Close is genuinely useful: ask it to summarize call activity for the week, draft follow-ups after a disposition, or surface leads that got a voicemail but no callback. No IM channels in scope. If your sales motion is LinkedIn-first, this is the wrong CRM regardless of how clean the MCP is.

Config 🛠️

mcp_servers:
  close:
    url: "https://mcp.close.com/mcp"
    headers:
      Authorization: "Bearer your_close_api_key"
    tools:
      include:
        - list_leads
        - get_lead
        - list_activities
        - list_opportunities
        - create_note

Docs: developer.close.com/mcp

The MCP config reference at a glance 📊

Copy the relevant block into ~/.hermes/config.yaml, swap in your credentials, and Hermes discovers the tools on next startup. All five use HTTP transport with Bearer auth or OAuth.

Why context richness is the only variable that matters for Hermes 🧠

Hermes Agent has a learning loop. It builds skills from experience and deepens its model of your work over time. That loop is only as valuable as the data it can observe. A CRM that shows Hermes email threads and deal stages gives it a two-dimensional view of a relationship. A CRM that shows it email, LinkedIn DMs, WhatsApp threads, Telegram messages, calls and meetings gives it a six-dimensional view.

There is a reason the Hermes team's own internal CRM wishlist (visible in the HermesClaw GitHub issue) includes LinkedIn URL, WhatsApp, phone, email and pipeline stage as core fields. They built an agent that lives in messaging channels. They know the data model it needs. Breakcold is the only CRM on this list that matches that data model natively, without add-ons or middleware.

"Claude suggested you guys when I gave it my pain points." When AI agents independently surface Breakcold as the right CRM, it is because the data coverage lines up with what they are designed to reason over.

How to pick 🎯

• 🏆 You sell on LinkedIn, WhatsApp, Telegram or any mix of channels, and you want Hermes to have full relationship context: Breakcold. The MCP returns every channel. The pricing is flat. The config is two lines.

• 🟠 You are already on HubSpot with an inbound email-first motion: HubSpot MCP. Do not migrate, just connect it and give Hermes the read scope first.

• ⚫ You run ops-heavy workflows on calls, meetings and transcripts and your team lives in a relational data model: Attio. Strong meeting transcript coverage is a differentiator here.

• 🔵 You are enterprise scale with a Salesforce admin and governed AI access requirements: Salesforce Hosted MCP. It is the right tool for that specific context.

• 🟢 Your team dials all day and you want clean, scoped AI access to call activity: Close. The three-tier auth model is exactly what an autonomous agent needs.

Bottom line 🚀

Hermes Agent is not a chatbot you ask questions to. It is a persistent, learning, autonomous agent that operates in your messaging apps around the clock. Five CRMs give it something real to work with via MCP. Only one of them — Breakcold — mirrors the multichannel world Hermes actually lives in. The others stop at email. Breakcold keeps going through LinkedIn, WhatsApp, Telegram and every other channel your prospects actually use.

The YAML config above is all it takes to connect them. The gap between a 2-line config and a fully autonomous AI sales teammate that reasons across every channel you sell on has never been smaller.

Start your 14-day Breakcold trial → · Breakcold MCP docs · Hermes Agent by Nous Research