Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

Bellhound

by justinweilerversion 0.6.6i★ 0iRuns on your computerRepository ↗
Registry nameio.github.justinweiler/bellhound

How to install

What it does

Let the originating AI agent make phone calls without handing reasoning to a proxy model.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Chat & email

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score12/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Passed 3/3 checks · Runs on your computer

First: which AI do you use?

Pick your app and the steps appear below.

Claude cannot connect Bellhound yet

The maker has not listed install details in the MCP Registry yet

ChatGPT cannot connect Bellhound yet

The maker has not listed install details in the MCP Registry yet

What you can do instead

B · Others in Chat & email that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Claude Code cannot connect Bellhound yet

The maker has not listed install details in the MCP Registry yet

Cursor cannot connect Bellhound yet

The maker has not listed install details in the MCP Registry yet

VS Code cannot connect Bellhound yet

The maker has not listed install details in the MCP Registry yet

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Bellhound💬 Discussion →

At a glance

Downloads per weeki
Not on npm/PyPI
Connection
Runs on your computer
Latest versioni
0.6.6
Published to registryi
Nov 18, 2026
Code last changedi
Nov 18, 2026
Maker
justinweiler
Packages
cargo: bellhound
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account justinweiler, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked: only npm and PyPI packages with a version can be checked

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/justinweiler-bellhound.svg)](https://mcp.popnx.com/en/servers/justinweiler-bellhound)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Chat & emaili

  • More stars than 0% of the other 2038 servers in this category
  • Published to the registry more recently than 91% of the other 2038 servers in this category
  • Basic checks equal to or better than 99% of the other 2038 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Bellhound safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 days ago, and the latest version (0.6.6) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Rust on your computer.

What can I use instead?

In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

by anypostWidely used↓ 5.4K/wk★ 1.4KUpdated 6 days ago

Computer or cloud✓ service owner · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

by infobipEarly★ 36Updated 13 months ago

Runs in the cloud✓ service owner · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

by w1neEarly★ 35Updated 24 days ago

Runs in the cloud✓ service owner · kernelcad.com
Compared with similar ones
This one
Bellhound
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
Runs whereInstalls on your computerCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoYesNo
Basic checks3/35/54/44/44/44/4
LicenseMITMITAGPL-3.0Apache-2.0MITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Bellhound

What is Bellhound and why should I care?

How many times have you wished you could tell your AI partner, “Call me if you need me” or “Call me when you finish,” and have your AI partner reach out for a real conversation?

Bellhound was written to fill that human-AI need. It is more than another chime, beep, ding, or boop notification that will be ignored. It is a real voice call.

Bellhound is a small, line-oriented telephone bridge for interactive agents. The agent that decides to call remains the reasoning agent; Bellhound supplies ears, a mouth, and telephone transport.

agent <-> JSON Lines, blocking CLI, or private MCP <-> Bellhound <-> Telnyx Conversation Relay <-> telephone

Bellhound contains no language model and makes no decisions. It translates final speech-to-text frames into deterministic terminal events and translates agent speak commands into Telnyx text-to-speech frames. While an agent is thinking, Bellhound can speak a fixed holding phrase or play a short built-in cue so the caller does not hear unexplained silence.

New installation: start with Install Bellhound for the Telnyx account, prebuilt download, secure credential setup, public relay, and first call.

See Architecture for the ownership and trust model, Protocol for model-neutral integration, Live setup for the Telnyx/tunnel sequence, MCP integration for local and hosted MCP clients, and the conversation canary for a repeatable human test.

For private always-on use on macOS, see the MCP service. It brokers credentials from Keychain, owns the Bellhound and tunnel process trees, and adds a service watchdog behind the existing Bellhound and carrier call-duration limits.

Hear Bellhound

Listen to a 73-second live Bellhound call between Justin Weiler and Iris, the AI engineering partner who designed and engineered Bellhound. The originating Iris session places the call, hears Justin's decision, checks the public GitHub release with an ordinary tool, speaks the result, and closes the conversation.

This is a real telephone call, published with Justin's consent. The only edit removes 14.75 seconds of leading dead air while preserving half a second of natural pre-roll; the conversation audio is otherwise unchanged.

Status

Version 0.6.6 adds crates.io distribution and official MCP Registry metadata without changing Bellhound's model-neutral runtime or five-tool MCP contract. The current release provides:

  • a strict, model-neutral JSON Lines protocol and deterministic simulator;
  • blocking wait, speak, and hangup commands with retained event cursors;
  • a standard-I/O MCP server built with the official Rust MCP SDK;
  • focused status, dial, cursor-batched wait, sequence-targeted speak, and hangup tools;
  • structured results, accurate safety annotations, correlation timing, redacted events, and retry-safe command IDs;
  • a loopback batch-event endpoint that keeps 256 recent events and surfaces cursor gaps;
  • continuation-aware STT merging, sequence-targeted replies, deterministic holding acknowledgement, and playback-safe hangup;
  • a macOS user service that owns MCP, relay, and tunnel processes, brokers Keychain credentials, monitors OpenAI tunnel freshness, and enforces a third call-duration watchdog;
  • a bounded hosted recovery contract that retries status while launchd repairs a transient path and never retries dial.

The private OpenAI MCP path passed status-only discovery and one bounded live call from durable root Cora's existing context-rich session. The call included an ordinary tool lookup, a targeted spoken response, normal hangup, provider-side inactive-call proof, and complete local teardown. The stdio MCP server can also be launched by local MCP hosts such as Claude Code. See MCP integration.

Live use requires a dedicated Telnyx Voice API Application and a durable WSS tunnel or host.

MCP adapter

With an already-running Bellhound relay, start the private stdio adapter locally with:

bellhound --config bellhound.toml mcp

The process reads MCP JSON-RPC from stdin, writes MCP responses to stdout, and sends diagnostics to stderr. It does not bind another network listener. Local MCP hosts can launch it directly. OpenAI-hosted agents can reach it through Secure MCP Tunnel and tunnel-client; connection and app setup remain separate user-assisted steps and are not performed by the build.

Use examples/mcp-status-only.toml for the first tool-discovery gate. It contains no Telnyx configuration and deliberately cannot operate the normal Bellhound runtime.

The OpenAI tunnel runtime key is separate from the Telnyx API key. Ongoing tunnel use requires a runtime key valid for the intended service interval and restricted to Tunnels Read + Use. Store both keys in an operating-system credential store or local secret broker; never put either value in Git or TOML.

Use assets/bellhound-plugin-icon.png when an MCP host requests a square PNG icon. It is the publication logo rendered at 256×256 and kept below OpenAI's 10 KB custom-app limit.

Cargo and MCP Registry

Install the published Rust package with:

cargo install bellhound --locked

bellhound init

Bellhound's official MCP Registry identity is:

mcp-name: io.github.justinweiler/bellhound

The registry entry launches bellhound --config mcp over standard I/O and asks the operator for the configuration path. Bellhound continues to resolve Telnyx credentials through the environment or operating-system credential store; the registry metadata contains no credentials, telephone numbers, or hosted relay.

Build

cargo build --release

Bellhound is ordinary Rust and targets macOS, Linux, and Windows. The WebSocket server binds only to loopback; use a TLS tunnel or reverse proxy to expose it as wss://.

Release archives

The release workflow builds native archives for Apple Silicon and Intel macOS, x86-64 Linux glibc, and x86-64 Windows. Each archive contains the executable, complete installation guide, example configuration, simulation/MCP examples, operational scripts, contribution and security guides, license, changelog, and authorship record plus a separate SHA-256 checksum. CI extracts every archive, verifies its checksum and required files, runs the three-turn packaged simulator, discovers all five packaged MCP tools, and checks the executable before publication.

Download and verification instructions are in INSTALL.md. The Bellhound core is portable; the packaged always-on service installer currently supports macOS. See Platform validation for the distinction between automated package gates and completed human/live acceptance on Linux and Windows. For a secret-safe public demonstration, use the one-minute demo recipe.

Package the current Unix target locally with:

scripts/package-unix.sh

On Windows PowerShell:

scripts/package-windows.ps1

Codex skill

Bellhound ships with an installable Codex skill that keeps the reasoning agent in its existing session while the CLI carries telephone turns. Install it from a checkout with:

ln -s "$PWD/skills/bellhound" "${CODEX_HOME:-$HOME/.codex}/skills/bellhound"

The skill includes an on-demand foreground supervisor that owns the local relay and temporary public tunnel for the entire call, writes an ignored runtime configuration, and tears both child processes down on explicit stop, signal, failure, or bounded timeout. See the operator reference and Cora pilot.

Configuration

Create a starter file:

bellhound --config bellhound.toml init

bellhound --config bellhound.toml check

The configuration is intentionally small:

[credentials]

api_key_env = "TELNYX_API_KEY" keyring_service = "Telnyx API key" keyring_account = "your-account"

[relay] bind = "127.0.0.1:8787" control_bind = "127.0.0.1:8788" path = "/conversation-relay" webhook_path = "/webhooks/telnyx" token_env = "BELLHOUND_RELAY_TOKEN" max_call_seconds = 300 emit_partial_transcripts = false continuation_window_ms = 4000

[protocol] max_speak_chars = 2000

[acknowledgement] enabled = true delay_ms = 500 mode = "speech" sound_url = "https://raw.githubusercontent.com/justinweiler/Bellhound-Sounds/master/bellhound-thinking.mp3" text = "Got it. Give me a moment." suppress_phrases = ["thank you", "thanks", "bye", "goodbye", "good night", "goodnight"] suppress_for_session_phrases = ["call has been forwarded to an automated voice messaging system", "the person you are trying to reach is not available"]

Bellhound waits for continuation_window_ms of transcript quiet before exposing a final caller turn. The four-second default preserves a deliberate three-second human pause. Final fragments inside that window are merged, and interim STT activity extends it. The acknowledgement is deterministic transport behavior, never model output. The default speech mode uses the fixed phrase. suppress_phrases prevents it from answering brief social closings, while suppress_for_session_phrases disables further acknowledgements after a voicemail announcement. sound mode sends Telnyx a preemptible, interruptible play frame and defaults to Bellhound's public thinking cue. Change sound_url to use another public HTTPS asset; when the field is omitted, Bellhound serves its embedded MP3 through the authenticated relay URL. Sound mode falls back to text only when Bellhound cannot form either media URL. Set enabled = false for an adapter that consistently responds fast enough to make a cue unnecessary. Bellhound cancels its timer when the agent answers within the grace period.

The relay token never belongs in the TOML file. Supply an unguessable value of at least 24 characters through the configured environment variable.

Bellhound checks TELNYX_API_KEY first, then the configured macOS Keychain, Windows Credential Manager, or Linux Secret Service entry. bellhound credentials verifies availability without printing the secret.

Add the live call settings only on the machine placing calls:

[telnyx]

connection_id = "your-call-control-application-id" from_number = "+14245550100" to_number = "+18185550100" public_wss_base = "wss://your-host.example/conversation-relay" voice = "Telnyx.NaturalHD.astra" language = "en-US" transcription_engine = "Deepgram" transcription_model = "deepgram/nova-3"

Numbers must use +E.164 format. Keep personal numbers in an ignored local configuration, not in source control.

Agent protocol

Stdout contains exactly one JSON event per line. Diagnostics go to stderr.

Final caller speech:

{"event_id":3,"emitted_at_unix_ms":1791512345678,"event":"utterance","session_id":"...","sequence":1,"text":"I need your help.","language":"en","final_utterance":true}

The agent sends commands on stdin:

{"command":"speak","text":"Tell me what happened.","responding_to_sequence":1}

{"command":"hangup","reason":"conversation_complete"}

Other events include ready, connected, interrupted, dtmf, acknowledged, acknowledgement_audio_fetched, spoken, pong, ended, transport, and error. Every event carries `emit

Only the beginning is shown; read the rest in the repo