原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Bellhound

作者:justinweiler版本 0.6.6i★ 0i在你的电脑上运行代码仓库 ↗
注册名称io.github.justinweiler/bellhound

安装方法

能做什么

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

作者提供的原文

  • 连接方式 在你的电脑上运行
  • 账号或密钥 无需密钥
  • 分类 聊天与邮件

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分12/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 Bellhound

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 Bellhound

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 聊天与邮件 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Bellhound

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 Bellhound

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 Bellhound

开发者尚未在 MCP 注册表中填写安装方式

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Bellhound 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
连接方式
在你的电脑上运行
最新版本i
0.6.6
发布到注册中心i
2026年11月18日
代码最后更新i
2026年11月18日
作者
justinweiler
软件包
cargo: bellhound
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

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

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 justinweiler 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于前天

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

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

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“聊天与邮件”中的其他服务器比较i

  • 星标数多于此分类中其他 2038 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 2038 个服务器的 91% 更新
  • 基础检查结果等于或优于此分类中其他 2038 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Bellhound 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于前天,最新版本(0.6.6)于前天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Rust。

有什么可以替代它?

同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

emailmd

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

作者:anypost广泛使用↓ 5432/周★ 13956天前更新

电脑或云端✓ 服务方 · emailmd.dev

Infobip MCP

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

作者:infobip起步阶段★ 3613个月前更新

在云端运行✓ 服务方 · infobip.com

kernelCAD

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

作者:w1ne起步阶段★ 3524天前更新

在云端运行✓ 服务方 · kernelcad.com
与相似项目对比
本项
Bellhound
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
运行位置需要安装在电脑上云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否是否
基础检查3/35/54/44/44/44/4
许可证MITMITAGPL-3.0Apache-2.0MITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分;其余内容请在仓库中阅读