callingly
Server Details
Lets AI agents get leads on the phone: call, send SMS, and schedule callbacks for sales teams.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
8 toolsadd_to_sequenceAdd a lead to a follow-up sequenceDestructiveInspect
Add a lead to a team's automated follow-up sequence — a voice + SMS series that keeps working the deal until it closes. The lead is enrolled in the chosen team's sequence and Callingly handles the calls, texts, retries, and timing. Use this to start a persistent follow-up cadence rather than a single call.
| Name | Required | Description | Default |
|---|---|---|---|
| No | The lead's email address. | ||
| source | No | Where this lead came from. Defaults to "MCP". | |
| company | No | The lead's company name. | |
| team_id | Yes | The id of the Callingly team (profile) whose follow-up sequence the lead should be added to. | |
| last_name | No | The lead's last name. | |
| first_name | No | The lead's first name. | |
| phone_number | Yes | The lead's phone number, ideally in E.164 format (e.g. +14155551234). |
get_recordingGet call recordings and transcriptsRead-onlyInspect
Read recordings, transcripts and outcomes of recent calls so your AI and CRM stay in sync. Returns each call's result, duration, recording URL, full transcript, and AI summary. Filter by lead_id to see how a specific lead's calls went, or fetch a single call by call_id.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of calls to return (1-50, default 10). | |
| call_id | No | Fetch a single call by its id. | |
| lead_id | No | Only return calls for this lead. |
make_ai_callHave the AI agent call a leadDestructiveInspect
Make a call to a lead with an AI voice agent. The AI agent calls the lead, qualifies them, answers questions, and warm-transfers the live call to a human rep when the lead is ready. The team must have an AI agent configured. Use this to qualify a lead automatically before a rep gets involved.
| Name | Required | Description | Default |
|---|---|---|---|
| No | The lead's email address. | ||
| source | No | Where this lead came from. Defaults to "MCP". | |
| company | No | The lead's company name. | |
| team_id | Yes | The id of the Callingly team (profile) whose AI agent should make the call. | |
| last_name | No | The lead's last name. | |
| first_name | No | The lead's first name. | |
| phone_number | Yes | The lead's phone number to dial, ideally in E.164 format (e.g. +14155551234). |
make_dispatch_callCall a lead nowDestructiveInspect
Make a dispatch call to a lead with a human rep. Callingly rings one of the team's sales reps — or the whole team — plays them the lead's details, then bridges them to the lead the second someone picks up. Use this for speed-to-lead when a lead should be contacted by a human right now.
| Name | Required | Description | Default |
|---|---|---|---|
| No | The lead's email address. | ||
| source | No | Where this lead came from. Defaults to "MCP". | |
| company | No | The lead's company name. | |
| team_id | Yes | The id of the Callingly team (profile) that should make the call. | |
| last_name | No | The lead's last name. | |
| first_name | No | The lead's first name. | |
| phone_number | Yes | The lead's phone number to dial, ideally in E.164 format (e.g. +14155551234). |
query_reportsQuery call reportsRead-onlyInspect
Query call reports for the account over a date range: call volume, connection rate, voicemail/missed counts, talk time, and per-rep performance. Use this to answer questions like "how many leads did we reach last week" or "which rep connected the most calls".
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | End date (YYYY-MM-DD) of the report range. Defaults to today. | |
| start | No | Start date (YYYY-MM-DD) of the report range. Defaults to 30 days ago. | |
| team_id | No | Limit the report to a single team (profile). |
schedule_callSchedule a callback with a leadDestructiveInspect
Schedule a call (callback) for a lead at a future time instead of calling immediately. When the scheduled time arrives, Callingly rings the team's sales reps and connects them to the lead, handling the dialing, reminders, and retries. Use this to book a callback for later.
| Name | Required | Description | Default |
|---|---|---|---|
| No | The lead's email address. | ||
| source | No | Where this lead came from. Defaults to "MCP". | |
| company | No | The lead's company name. | |
| team_id | Yes | The id of the Callingly team (profile) that should make the call. | |
| last_name | No | The lead's last name. | |
| first_name | No | The lead's first name. | |
| phone_number | Yes | The lead's phone number to dial, ideally in E.164 format (e.g. +14155551234). | |
| scheduled_at | Yes | When the call should be placed, as a date/time string in the account's timezone (e.g. "2026-06-10 14:30"). Past times are bumped to now. |
schedule_smsSchedule a text to a leadDestructiveInspect
Schedule an SMS text message to an existing lead at a future time instead of sending immediately. When the scheduled time arrives, Callingly renders and sends the message from your phone number. Use this to time a reminder or follow-up to the lead's timezone.
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | The text message body. Supports Callingly merge fields and is rendered when the message is sent. | |
| send_at | Yes | When the text should be sent, as a date/time string in the account's timezone (e.g. "2026-06-10 09:00"). Past times are bumped to now. | |
| sms_number | Yes | One of your Callingly phone numbers to send the text from. | |
| phone_number | Yes | The lead's phone number to text. The lead must already exist in your account. |
send_smsText a leadDestructiveInspect
Send an SMS text message to an existing lead from one of your Callingly phone numbers. The lead must already exist in your account (matched by phone number). Use this to introduce an agent, confirm a callback, or follow up.
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | The text message body. Supports Callingly merge fields. | |
| sms_number | Yes | One of your Callingly phone numbers to send the text from. | |
| phone_number | Yes | The lead's phone number to text. The lead must already exist in your account. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!