How to integrate Callingly MCP with Claude Code

Manage your Callingly directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Callingly logoCallingly
Api Key

Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources.

29 Tools

Introduction

Manage your Callingly directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Callingly with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Callingly to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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.

Connecting Callingly via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Callingly) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Callingly account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['callingly'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http callingly-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Callingly. This URL will be used to connect Claude Code to Callingly.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Callingly
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Callingly MCP to Claude Code

bash
claude mcp add --transport http callingly-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (callingly-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Callingly MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your callingly-composio entry in the list
  • This confirms that Claude Code can now access Callingly tools

If everything is wired up, you should see your callingly-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Callingly

The first time you try to use Callingly tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Callingly
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Callingly authorization flow
  • Return to the terminal and start using Callingly through Claude Code

Once authenticated, you can ask Claude Code to perform Callingly operations in natural language. For example:

  • "Activate a client account for onboarding"
  • "Create an outbound call to new lead"
  • "Get agent schedule for next week"

Complete Code

Here's the complete code to get you started with Callingly and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['callingly'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http callingly-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Callingly with Claude Code using Composio's MCP server. Now you can interact with Callingly directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Callingly operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Callingly operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every Callingly action and event your agent gets out of the box.

Activate/Deactivate Client Account

Tool to activate or deactivate a client account.

Create Agent

Tool to create a new agent.

Create Outbound Call

Creates a new outbound call record and initiates a real outbound call, which incurs cost — ensure explicit user authorization and compliance with applicable consent and telemarketing regulations before use.

Create Client

Creates a new client account in Callingly.

Create Team

Tool to create a new team.

Create Webhook

Tool to create a new webhook for call or lead events.

Delete Agent

Permanently delete an agent from a Callingly account.

Delete Client

Tool to delete a client.

Delete Lead

Tool to delete a lead by ID.

Delete Webhook

Tool to delete a webhook.

Get Agent Schedule

Tool to retrieve the availability schedule for a specific agent.

Get Call

Retrieves detailed information about a specific call by its unique ID.

Get Lead

Tool to retrieve details of a specific lead by its ID.

Get Team

Tool to retrieve details of a specific team.

Get Webhook

Tool to retrieve details of a specific webhook by its ID.

List Calls

Tool to list calls.

List Clients

Tool to list clients.

List Leads

Tool to list leads based on provided filters like date range or phone number.

List Teams

Tool to list teams.

List Team Users

Retrieve all agents assigned to a specific team in Callingly.

List Users

Tool to retrieve a list of agents.

List Webhooks

Tool to list configured webhooks.

Remove Team Agent

Tool to remove a specific agent from a team.

Update Agent

Tool to update an existing agent's details.

Update Lead

Tool to update an existing lead's information.

Update Agent Schedule

Tool to update an agent's availability schedule.

Update Team Agent Settings

Tool to update settings (priority, capacity) for a specific team agent.

Update Team Users

Updates the list of agents assigned to a team.

Update Webhook

Updates an existing webhook's configuration by ID.

FAQ

Frequently asked questions

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.

Yes, you can. Claude Code 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.

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.

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.

Start with Callingly.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Callingly tool your agent needs.Free to start.

Start building