Callwright

com.topnessPublished by topness.comv1.0.4Updated Oct 27, 2026

Self-hosted MCP voice agent that places phone calls on your behalf via Retell.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Self-hosted MCP server that lets an assistant place phone calls through Retell voice agents and fire a Claude cloud Routine trigger.

What you can do
  • Place outbound phone calls through Retell voice agents on the assistant's behalf.
  • Receive Retell webhook events at a public base URL so call activity can be routed back into the workflow.
  • Trigger a configured Claude cloud Routine endpoint, optionally with a dedicated bearer token.
  • Keep runtime state such as trigger deduplication in a persistent data directory.
  • Serve MCP over HTTP on a configurable port, with an optional bearer token for clients.
When to use it
Use it when you want an assistant to make real outbound phone calls with a Retell voice agent, or to connect call events to a Claude Routine, and you are willing to self-host the process on a desktop machine.
Requirements
Runs as a local process (npm package callwright, streamable-http transport), desktop only. Needs a Retell secret API key in RETELL_API_KEY, a port via PORT (default 8787), and a persistent directory via CALLWRIGHT_DATA_DIR. A publicly reachable base URL in CALLWRIGHT_PUBLIC_URL is needed for Retell webhooks. Optional: CLAUDE_ROUTINE_URL and CLAUDE_ROUTINE_TOKEN, and MCP_AUTH_TOKEN when exposed beyond localhost.
Before you install
It places real phone calls, which can cost money and contact third parties. It holds a Retell API key (RETELL_API_KEY) and optionally a Claude Routine bearer token (CLAUDE_ROUTINE_TOKEN); keep them server-side. Exposing the HTTP endpoint beyond localhost requires MCP_AUTH_TOKEN, and without it clients may connect unauthenticated. A public URL is shared with Retell for webhook delivery.

Installation

In SourceWeft

  1. Open Callwright 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.4LatestSep 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.