Callingly
Callingly is a lead response management software that automates immediate call and text follow-ups to new leads, integrating seamlessly with various CRMs and lead sources to enhance sales team responsiveness and conversion rates.
Verdict
Common use cases
- Onboard new client accounts from chat
- Register sales agents after hiring
- Log outbound call records in bulk
- Set up webhooks for call events
- Deactivate clients after contract ends
Integration
- Vendor
- Callingly
- Category
- other
- Auth
- API_KEY
- Tools
- 27
- Composio slug
callingly
Tools
- Activate/Deactivate Client Account
Tool to activate or deactivate a client account. use when you need to toggle client access after onboarding or offboarding. example: "activate client 123" or "deactivate client 456".
- Create Agent
Tool to create a new agent. use when you need to register an agent in callingly after gathering their account id and contact details.
- Create Client
Tool to create a new client. use when adding a new client to your callingly account.
- Create Outbound Call
Tool to create a new outbound call record. use after gathering call and lead details.
- Create Team
Tool to create a new team. use when setting up a team configuration before adding agents.
- Create Webhook
Tool to create a new webhook for call or lead events. use when you need to receive real-time notifications on specific events. example: "create a webhook for call completed events to http://example.com/callback".
- Delete Agentdestructive
Tool to delete an agent. use when permanently removing an agent after confirming the agent id.
- Delete Clientdestructive
Tool to delete a client. use when you need to remove an existing client from your account after confirming its id.
- Delete Webhookdestructive
Tool to delete a webhook. use when permanently removing a webhook by its id.
- Get Agent Schedule
Tool to retrieve the availability schedule for a specific agent. use when you need to know which days and times the agent is available.
- Get Call
Tool to retrieve details of a specific call by its id. use when you need detailed metadata of a call record after confirming call id.
- Get Lead
Tool to retrieve details of a specific lead by its id. use when you need full lead details before follow-up actions.
- Get Team
Tool to retrieve details of a specific team. use after obtaining the team id to fetch its configuration details.
- Get Webhook
Tool to retrieve details of a specific webhook by its id. use when you need to inspect a webhook's configuration before modifying or deleting it.
- List Calls
Tool to list calls. use when you need to retrieve multiple call records with optional filters such as date range, team, and pagination after identifying the need for a collection of calls.
- List Clients
Tool to list clients. use when you need to retrieve all clients associated with your account.
- List Leads
Tool to list leads based on provided filters like date range or phone number. use after confirming filter criteria when bulk lead retrieval is needed.
- List Teams
Tool to list teams. use when you need to retrieve all teams associated with your account.
- List Team Users
Tool to retrieve a list of agents associated with a specific team. use when you need to inspect the team's users before further agent management tasks.
- List Users
Tool to retrieve a list of agents. use when you need to see all agents available under the authenticated account, optionally filtering by a specific client account.
- List Webhooks
Tool to list configured webhooks. use when you need to retrieve all webhooks configured in your account to review or manage them.
- Remove Team Agentdestructive
Tool to remove a specific agent from a team. use when you need to disassociate an agent from a team after confirming both team and agent ids.
- Update Agent
Tool to update an existing agent's details. use when you need to modify agent information post-creation.
- Update Agent Schedule
Tool to update an agent's availability schedule. use when you need to set or override an agent's daily availability times.
- Update Team Agent Settings
Tool to update settings (priority, capacity) for a specific team agent. use when adjusting an agent's priority or call capacity after team configuration.
- Update Team Users
Tool to update the list of agents assigned to a team. use when reassigning team members before call dispatch.
- Update Webhook
Tool to update an existing webhook's configuration. use when you need to change settings like target url or filters after confirming webhook id.
Setup
Setup guide
- 1Open your Switchy workspace and navigate to Settings > Integrations > Add MCP.
- 2Select Callingly from the catalog and choose API Key as the authentication method.
- 3Log into your Callingly dashboard, go to Settings > API, and generate a new API key with full read-write permissions.
- 4Paste the key into Switchy's connection form and click Connect.
- 5Switchy will verify the key and confirm the connection within a few seconds.
- 6Open any Space, type '@Callingly list all agents' and send—if you see agent records returned, the integration is live.
- 7You can now @mention Callingly in any message to create clients, register agents, log calls, or set up webhooks.
What teammates see: by default, memories from Callingly are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create New Client
@Callingly create a new client named Acme Corp with contact email sales@acme.com and phone +1-555-0199Open in a Space →
Register Sales Agent
@Callingly create an agent with account ID 789, email john@example.com, and assign them to the outbound sales teamOpen in a Space →
Log Outbound Call
@Callingly create an outbound call record for lead ID 456, duration 8 minutes, outcome 'qualified', notes 'interested in enterprise plan'Open in a Space →
Set Up Call Webhook
@Callingly create a webhook for 'call completed' events that posts to https://myapp.example.com/webhooks/callsOpen in a Space →
Deactivate Client Account
@Callingly deactivate client account 123 and confirm the change was appliedOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Callingly show me all active agents in the sales team and their current call status
Here's a summary of active agents in your sales team: Agent Sarah Chen (ID: ag_892) is currently on an active call with lead LD-4521, started 8 minutes ago. Agent Marcus Williams (ID: ag_903) completed their last call 12 minutes ago and is available. Agent Priya Patel (ID: ag_915) is available, last call ended 45 minutes ago. All three agents are active and properly configured with their callback numbers. This data reflects the current state as of this query.
This example demonstrates Callingly's agent monitoring capabilities. Note that call status is a point-in-time snapshot — agent availability changes constantly. You'll need appropriate API key permissions to view agent details across your account, and real-time updates require webhook configuration rather than polling.
@Callingly create a new outbound call for lead Emma Rodriguez at +1-555-0142, assign it to agent ag_903, priority high
Outbound call created successfully. Call ID: call_7821 has been queued for lead Emma Rodriguez (+1-555-0142) and assigned to agent Marcus Williams (ag_903). Priority set to high — this call will be prioritized in the agent's queue. The call record is now active in your Callingly dashboard. Agent ag_903 will receive notification of this queued call according to your team's routing configuration.
This showcases Callingly's outbound call creation workflow. The MCP creates the call record but doesn't initiate the actual phone connection — that happens through Callingly's dialer when the agent is ready. Be aware that invalid phone numbers or inactive agent IDs will cause the creation to fail, so validate inputs first.
@Callingly review all webhook configurations and suggest which events we should monitor for our sales pipeline reporting
You currently have 2 webhooks configured: one for 'call.completed' events pointing to your CRM endpoint, and one for 'lead.updated' events to your analytics platform. For comprehensive sales pipeline reporting, I recommend adding webhooks for: (1) 'call.missed' events to track follow-up opportunities, (2) 'agent.status_changed' events to monitor team availability patterns, and (3) 'call.recording_ready' events if you're analyzing conversation quality. These additions would give you end-to-end visibility from lead assignment through call completion and agent performance.
This example pairs Callingly's webhook management tools with AI reasoning about your workflow needs. The MCP can list and create webhooks, but the AI's suggestions depend on understanding your business context — provide details about your reporting goals for better recommendations. Remember that each webhook endpoint must be publicly accessible and return proper HTTP responses to avoid delivery failures.
Use-case deep-dives
When Callingly wins for multi-client call center setup
A 12-person BPO managing outbound sales for 8 different clients needs to spin up new agent accounts, assign them to client-specific teams, and route call dispositions back to each client's CRM. Callingly's MCP is the right call here because it exposes the full account-provisioning stack—create agents, create teams, activate client accounts, wire up webhooks—so you can script the entire onboarding flow in one Switchy session instead of clicking through the vendor UI 96 times. The auth is straightforward API key, and the 27 tools cover the full lifecycle from setup to teardown. If you're running fewer than 3 clients or your onboarding happens once a quarter, the manual UI is faster. But if you're adding 5+ agents a month across multiple client accounts, this MCP pays for itself in the first week.
When this MCP speeds up integration troubleshooting
A 3-person RevOps team at a Series A SaaS company is trying to figure out why call-completed events aren't landing in their Slack channel. The Callingly MCP lets them list existing webhooks, check the endpoint URLs, delete stale hooks, and create test webhooks—all from the same Switchy chat where they're debugging the payload format with their engineer. This beats toggling between the Callingly dashboard, Postman, and Slack because the MCP keeps the full context in one thread. The trade-off: if your webhook config is static and you set it once at launch, you don't need this. But if you're iterating on event-driven workflows or troubleshooting why leads aren't syncing, the MCP cuts your debug loop from 20 minutes to 4.
When Callingly's MCP handles account teardown safely
A fractional COO is offboarding a churned client from a 6-person call center and needs to deactivate the client account, delete 4 agents who only worked that client, and archive the team without touching active accounts. The Callingly MCP is the safer play here because it surfaces the delete and deactivate tools with confirmation prompts, and you can script the sequence in Switchy so nothing gets skipped. The alternative—manual clicks in the vendor UI—risks leaving orphaned agent records or forgetting to deactivate billing. If you offboard clients once a year, the manual path is fine. But if you're churning 2+ clients a quarter or running a multi-tenant operation, this MCP turns a 45-minute checklist into a 6-minute scripted teardown.
Frequently asked
What does the Callingly MCP do in Switchy?
It lets your AI assistant manage Callingly's outbound calling infrastructure — creating agents, clients, and teams, logging call records, and setting up webhooks for real-time event notifications. You can onboard new clients, activate or deactivate accounts, and orchestrate call workflows without leaving the chat. Think of it as programmatic access to Callingly's admin and operations layer.
Do I need admin access to connect Callingly?
Yes. The MCP uses an API key, which Callingly typically issues to account administrators. You'll need permission to create agents, clients, and webhooks — operations that modify your Callingly account structure. If you're not an admin, ask whoever manages your Callingly subscription to generate the key and share it with your Switchy workspace owner.
Can the Callingly MCP actually make phone calls?
No. It creates outbound call records and manages the infrastructure around calls — agents, clients, teams, webhooks — but it doesn't dial numbers or handle live call audio. For that, you still use Callingly's native dialer or API. The MCP is for orchestration and admin tasks, not replacing your calling software.
Why use this instead of Callingly's dashboard?
Speed and automation. If you onboard ten clients a week or need to bulk-create agents, typing "create client Acme Corp" in Switchy is faster than clicking through forms. The MCP also lets you chain operations — create a client, add three agents, set up a webhook — in one conversation. For one-off tasks, the dashboard is fine.
Who on my team should connect Callingly to Switchy?
Your operations lead or whoever manages Callingly day-to-day. They already know which clients need activating, which agents to onboard, and how your webhook flows work. Give them access to the Switchy workspace with Callingly connected, and they can handle admin tasks conversationally instead of context-switching to the Callingly UI.