How to integrate Callingly MCP with Hermes

Callingly logo
Hermes logo
divider

Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Callingly account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Callingly with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Callingly with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Callingly

Ask your agent to connect to Callingly, or simply request any Callingly-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Callingly connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Callingly or request any Callingly-related task. It will prompt you to authenticate and authorize access.

5. Done!

What is the Callingly MCP server, and what's possible with it?

The Callingly MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Callingly account. It provides structured and secure access to your Callingly environment, so your agent can automate lead follow-ups, manage agents and clients, trigger outbound calls, and keep your sales workflows moving without manual intervention.

  • Automated outbound call creation: Instantly generate outbound call records so your team can respond to new leads within seconds without lifting a finger.
  • Agent and team management: Let your agent create, delete, or update agents and teams as your sales organization changes and grows.
  • Client onboarding and offboarding: Seamlessly add, activate, deactivate, or remove client accounts as your business requires—no more manual data entry.
  • Real-time webhook setup: Set up and delete webhooks to receive instant notifications for specific call or lead events, keeping your CRM and other tools in sync.
  • Availability and scheduling insights: Retrieve agent schedules to optimize call assignments and guarantee leads get connected when agents are actually available.

Supported Tools & Triggers

Tools
Activate/Deactivate Client AccountTool to activate or deactivate a client account.
Create AgentTool to create a new agent.
Create Outbound CallTool to create a new outbound call record.
Create ClientTool to create a new client.
Create TeamTool to create a new team.
Create WebhookTool to create a new webhook for call or lead events.
Delete AgentTool to delete an agent.
Delete ClientTool to delete a client.
Delete WebhookTool to delete a webhook.
Get Agent ScheduleTool to retrieve the availability schedule for a specific agent.
Get CallTool to retrieve details of a specific call by its id.
Get LeadTool to retrieve details of a specific lead by its id.
Get TeamTool to retrieve details of a specific team.
Get WebhookTool to retrieve details of a specific webhook by its id.
List CallsTool to list calls.
List ClientsTool to list clients.
List LeadsTool to list leads based on provided filters like date range or phone number.
List TeamsTool to list teams.
List Team UsersTool to retrieve a list of agents associated with a specific team.
List UsersTool to retrieve a list of agents.
List WebhooksTool to list configured webhooks.
Remove Team AgentTool to remove a specific agent from a team.
Update AgentTool to update an existing agent's details.
Update Agent ScheduleTool to update an agent's availability schedule.
Update Team Agent SettingsTool to update settings (priority, capacity) for a specific team agent.
Update Team UsersTool to update the list of agents assigned to a team.
Update WebhookTool to update an existing webhook's configuration.

Way Forward

With Callingly connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

How to build Callingly MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Callingly MCP?

With a standalone Callingly MCP server, the agents and LLMs can only access a fixed set of Callingly tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Callingly and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Hermes?

Yes, you can. Hermes fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Callingly tools.

Can I manage the permissions and scopes for Callingly while using Tool Router?

Yes, absolutely. You can configure which Callingly scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Callingly data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.