EchoCall

de.echocallPublished by echocall.deOfficial publisherv1.19.0Updated Nov 7, 2026

Run EchoCall AI phone and chat agents from ChatGPT or Claude: calls, agents, knowledge and numbers.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

EchoCall lets an assistant run EchoCall AI phone and chat agents — calls, agents, knowledge and numbers — from ChatGPT or Claude.

What you can do
  • Manage AI phone and chat agents, including their configuration and operation
  • Place and handle calls through the EchoCall platform
  • Maintain the knowledge that agents draw on
  • Manage phone numbers used by the agents
  • All of this is driven from the assistant via a hosted remote endpoint
When to use it
Useful when you want to operate EchoCall's AI calling and chat agents without leaving ChatGPT or Claude, for example to set up or adjust agents, keep their knowledge current, or work with the numbers they use.
Requirements
A remote MCP endpoint at hub.echocall.de over streamable HTTP, with OAuth sign-in to an EchoCall account required. No local package, environment variables or headers are declared.
Before you install
Access is tied to your EchoCall account through OAuth, so the assistant can act on that account's agents, knowledge and numbers. The tool list is not published, so confirm which actions place calls, change agent settings or modify data before granting access. Calls and chat may involve third-party participants and their data.

Installation

In SourceWeft

  1. Open EchoCall 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/de.echocall%2Fechocall/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": {
    "echocall": {
      "type": "http",
      "url": "https://hub.echocall.de/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.19.0LatestNov 7, 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.