
Sable Platform + HyperDX Observability
io.github.sable-inc由 GitHub 账号 sable-inc 发布v0.3.0更新于 Oct 25, 2026
Manage Sable AI voice agents, query HyperDX logs and metrics, and deploy — all from your IDE
概览
面向 Sable AI 语音代理平台的本地 MCP 服务器,让助手管理代理、旅程、知识库、部署,并查询 HyperDX 可观测性数据。
- 可以做什么
- 列出、创建、更新和删除语音代理与旅程,并读取其详情和连接信息。搜索、导入、同步和删除知识库条目。列出配置、通话记录以及会话和阶段分析数据。查看部署历史、触发部署与回滚,并检查 API 健康状态。向 Sable API 发送原始 API 请求。可选地查询 HyperDX 的日志、指标、仪表盘和告警。
- 适用场景
- 当你在 IDE 助手中使用 Sable 语音代理平台,希望不离开编辑器就查看或修改代理、旅程、知识库和部署,或同时获取 HyperDX 可观测性数据时适用。
- 运行要求
- 以本地二进制运行,可通过 Homebrew、Go install 或下载发布包安装;MCP 服务器由 anvil mcp serve 命令启动。需要 Sable 服务令牌(通过 anvil auth login 保存)、在配置文件中设置默认组织和 API 地址,并能访问 Sable API。HyperDX 工具还需通过 anvil settings 或 HYPERDX_API_KEY 环境变量提供 HyperDX API 密钥。
安装
在 SourceWeft 中
- 打开 控制台中的 Sable Platform + HyperDX Observability,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Anvil
Command-line interface and MCP server for the Sable AI voice agent platform.
Quick Start (2 minutes)
Install
Option 1: Homebrew (recommended)
Option 2: Go Install
This puts the anvil binary in $GOPATH/bin (usually ~/go/bin). Make sure that's in your $PATH:
Option 3: Download Binary (no Go required)
Download the latest release from GitHub Releases:
macOS (Apple Silicon):
macOS (Intel):
Linux (amd64):
Or download manually from the Releases page.
Option 4: Build from Source
Verify Installation
Authentication
Anvil authenticates with sable-api using a service token:
Credentials are stored in ~/.config/anvil/credentials.json (file permissions: 0600).
To get a service token, ask your team admin or generate one in the Sable Platform dashboard.
Configuration
Create ~/.config/anvil/config.yaml:
Override any setting with flags:
Shell Completions
Anvil has dynamic tab completions that suggest real resource names from the live API.
Setup (one-time, permanent)
Zsh (default on macOS):
Bash:
Fish:
PowerShell:
What You Get
After setup, press TAB anywhere:
Completions fetch live data from the API using your stored token. If you're not authenticated, it gracefully shows no suggestions (no errors).
FAQ
Do I need to regenerate completions when anvil or my shell updates?
No. The source <(anvil completion ...) pattern re-generates on every new shell session automatically. For Fish, re-run the file write command after updating anvil if new commands were added.
Commands
Agents
Journeys
Knowledge Base
Config-as-Code
Analytics & Transcripts
Deployments
LiveKit
Forge (Version Management)
Video Processing
Utilities
Config-as-Code Workflow
Pull a config, edit locally, validate, and push:
MCP Server (for AI Assistants)
Anvil includes an MCP server (28 Sable tools + 5 HyperDX observability tools) for AI coding assistants like Claude Code, Cursor, Windsurf, etc.
One-Time Setup
Add to Cursor
Paste this in your browser to install with one click:
Or add manually to .cursor/mcp.json:
Add to Claude Code
No secrets in the config -- anvil reads credentials from ~/.config/anvil/.
Other Editors (Windsurf, etc.)
Add the same JSON config to your editor's MCP settings file.
Sable Tools (28)
HyperDX Observability Tools (5, optional)
Enabled when anvil settings set-hyperdx <key> has been run or HYPERDX_API_KEY env var is set.
Releasing New Versions
Anvil uses goreleaser with GitHub Actions for automated releases.
Creating a Release
GitHub Actions will automatically:
- Build binaries for Linux, macOS, and Windows (amd64 + arm64)
- Create a GitHub Release with downloadable archives
- Generate checksums and a changelog
- Publish to the Homebrew tap (
sable-inc/homebrew-tap) - Publish to the MCP Registry (discoverable in Claude Code / Cursor)
Team members can then upgrade via:
Snapshot Build (local testing)
Development
Requires:
- Go 1.26+
- golangci-lint v2 (for
make lint) - Running sable-api instance (for
make generate)
CI/CD
GitHub Actions runs automatically:
- CI (
.github/workflows/ci.yml): build + test + lint on every push and PR - Release (
.github/workflows/release.yml): goreleaser on version tags (v*)
来源:README.md,提交 5e47ea7
工具
0版本历史
1- v0.3.0最新Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。