pebble-index-mcp
Enables voice captures from a smart ring to search and append notes in a local Obsidian vault and query an OpenAI-compatible AI agent, returning answers as phone notifications.
README
pebble-index-mcp
MCP bridge that exposes a local Obsidian vault and a Hermes Agent instance to the Pebble Index 01 smart ring's double-click MCP sandbox. Voice captures from the ring are routed by the Pebble app's cloud agent into this server's tools, and the answer comes back as a phone notification.
Architecture
[Index ring] → [Pebble app] → [Pebble cloud agent] → [this MCP server]
├─ vault tools (local files)
└─ ask_hermes → Hermes API server
- The server speaks MCP over Streamable HTTP (official
mcpSDK, FastMCP). - Every request must carry a bearer token; anything else gets 401.
- FastMCP's DNS-rebinding protection is on: allowed hosts are loopback plus
anything listed in
MCP_ALLOWED_HOSTS. - The public exposure is a cloudflared tunnel to the loopback port; no cloud infrastructure is required beyond that.
Components
| Path | Role |
|---|---|
src/pebble_index_mcp/vault.py |
Vault: path-sandboxed read/append + ripgrep search over the vault. All paths resolve inside the vault root; absolute paths, .. traversal, and symlink escapes are rejected. Appends are append-only, timestamped, and never overwrite. |
src/pebble_index_mcp/hermes.py |
HermesClient: forwards questions to an OpenAI-compatible chat completions endpoint with a short-answer system hint. Maps timeouts/transport failures/bad shapes onto HermesTimeout/HermesError. |
src/pebble_index_mcp/server.py |
FastMCP app: registers the four tools and the ring_persona prompt, wraps the streamable-http app in bearer auth (constant-time compare) and configures host allow-listing. |
Tools
vault_search(query, max_results=5)— case-insensitive text search; returnspath: excerptlines.vault_read(note_path, max_chars=1500)— reads the head of a note.vault_append(note_path, text)— appends a timestamped- HH:MM textline, creating the note if needed.ask_hermes(question)— forwards to the Hermes API server; 60s timeout with an honest acknowledgment on miss.
Security
- Auth: static bearer token (
MCP_BEARER_TOKEN), constant-time compared, required on every request. An empty token fails closed (all requests 401) and logs a warning at startup. - Transport: TLS terminates at the tunnel edge; the origin listens on loopback only.
- Host validation: DNS-rebinding protection rejects requests whose Host header is not loopback or in
MCP_ALLOWED_HOSTS. - Path sandbox: vault tools resolve all paths and require them to stay inside the vault root; symlink escapes are rejected and file opens use
O_NOFOLLOWon the final component. The sandbox guards against accidental and remote misuse; a hostile local process that races a parent-directory swap can still win (documented TOCTOU boundary — the vault is assumed to be a trusted single-user directory). - Config is read once at import: rotating the bearer token or changing allowed hosts requires a service restart.
- Secrets: the Hermes API key and MCP token live in a 0600 env file outside this repo, never in code, logs, or commits.
- Privacy note: recordings routed through the double-click sandbox transit the Pebble app's cloud agent. Single-click captures stay on-device. Sensitive thoughts belong on single-click.
Configuration (env)
| Var | Default | Purpose |
|---|---|---|
VAULT_PATH |
— | Required. Vault root for the file tools |
MCP_HOST / MCP_PORT |
127.0.0.1 / 8765 |
Listen address |
MCP_BEARER_TOKEN |
— | Required; request auth token |
MCP_ALLOWED_HOSTS |
— | Comma-separated extra allowed Host values (the public tunnel hostname goes here) |
HERMES_API_URL |
http://127.0.0.1:8642/v1/chat/completions |
ask_hermes target |
HERMES_API_KEY |
— | API server bearer key |
RING_MODEL |
pebble-ring |
Model alias sent upstream (map it to a cheap model via the API server's model_routes) |
RING_PERSONA_FILE |
— | Optional path to a text file replacing the generic cloud-agent persona |
HERMES_API_URL accepts any OpenAI-compatible chat completions endpoint, so
ask_hermes works against OpenRouter directly, Ollama, or any other
compatible API — Hermes is just the default.
Development
python3 -m venv .venv
.venv/bin/pip install -e ".[dev]"
.venv/bin/pytest -v
Run locally: set the env vars above and python -m pebble_index_mcp.server.
Deployment
deploy/ contains a systemd user unit template and a cloudflared tunnel
template (hostname and credentials filled in on the host, not in this repo).
See docs/ring-checklist.md for the phone-side setup and test matrix.
License
MIT — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。