Looply

io.github.xie38388Published by GitHub account xie38388v1.0.1Updated Oct 30, 2026

Looply AI call center MCP Server - manage calls, leads, contacts, and analytics.

VerifiedSTDIODesktop onlyDatabasesData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Looply connects an AI assistant to a Looply AI call center to manage calls, leads, contacts and analytics.

What you can do
  • Manage calls in the Looply AI call center
  • Work with leads and contacts
  • Retrieve call center analytics
  • Query the underlying MySQL database directly using the configured connection string
  • Authenticate against a self-hosted Looply instance via its API key and base URL
When to use it
Useful when you run a Looply AI call center instance and want an assistant to look up or manage calls, leads and contacts, pull analytics, or query the related MySQL data without switching tools.
Requirements
Runs locally as an npm package (looply-mcp-server) over stdio, desktop only. Needs a Looply instance URL in LOOPLY_BASE_URL, a Looply API key in LOOPLY_API_KEY generated from the dashboard, and a MySQL connection string in DATABASE_URL. Network access to both the Looply instance and the database.
Before you install
Requires two secrets: LOOPLY_API_KEY and a full MySQL connection string in DATABASE_URL, which grants direct database access. The server can change call center records such as calls, leads and contacts, so review actions before they run. Direct database queries may expose or alter production data.

Installation

In SourceWeft

  1. Open Looply in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.