Callingly

com.callinglyPublished by callingly.comOfficial publisherv1.0.0Updated Oct 24, 2026

Lets AI agents get leads on the phone: call, send SMS, and schedule callbacks for sales teams.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Lets an AI assistant place phone calls, send SMS messages, and schedule callbacks to sales leads through Callingly.

What you can do
Callingly exposes its lead-engagement platform to AI agents so they can reach sales leads by phone. According to the registry description, it supports calling leads, sending SMS messages, and scheduling callbacks. It runs as a remote MCP endpoint hosted by the provider rather than as a local package.
When to use it
Consider it when a sales or outreach workflow should let an assistant contact leads directly by phone or text and arrange follow-up calls. It is aimed at teams already using Callingly for lead engagement rather than at general-purpose calling.
Requirements
A remote MCP client that can connect to the provider's hosted endpoint over streamable HTTP. The manifest declares no authentication, environment variables, or headers, so any account or credential requirements are not documented here.
Before you install
This server can contact real people: it places calls and sends SMS messages to leads, which may cost money and may be subject to consent, do-not-call, and messaging regulations. The manifest declares no authentication, so confirm how access to the endpoint is actually controlled before connecting it to a live lead list.

Installation

In SourceWeft

  1. Open Callingly in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.callingly%2Fcallingly/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "callingly": {
      "type": "http",
      "url": "https://api.callingly.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.