rikkahub-history-mcp
Read-only MCP bridge for searching and browsing RikkaHub app conversations through its Web API.
README
RikkaHub History MCP
A read-only MCP bridge for searching conversations from the official RikkaHub app through its Web API. It does not require a modified APK, root access, or Room database migration.
Features
recent_conversations— list recent conversations with lightweight metadata.search_conversations— use RikkaHub's built-in full-text index.get_conversation_context— read a bounded window around a search hit.- Reads only the currently selected message branch.
- Returns USER/ASSISTANT text only; reasoning, tool calls/results, and attachments are omitted.
- Resolves
rikkahub.localwith mDNS, so a phone DHCP address change normally needs no reconfiguration. - Automatically refreshes RikkaHub's Web JWT.
- Streamable HTTP mode can be protected with a separate Bearer token.
Requirements
- Python 3.10+
- RikkaHub Web Server enabled and reachable on the same LAN
- RikkaHub Web JWT/password enabled (recommended)
Install
python -m venv .venv
# Windows
.venv\Scripts\python -m pip install -e .
# Linux/macOS
.venv/bin/python -m pip install -e .
Configure RikkaHub Web
In RikkaHub, enable the Web Server and set an access password. The default Web port is 8080.
The bridge first tries:
http://rikkahub.local:8080
It re-resolves mDNS after failures and can retain the last successful phone IP as a short-lived fallback.
Run with Streamable HTTP
Copy start_http.example.ps1 to the ignored start_http.ps1, then replace its placeholders. Alternatively, set the variables from .env.example in your process environment.
Important variables:
| Variable | Description |
|---|---|
RIKKAHUB_WEB_PASSWORD |
RikkaHub Web access password |
RIKKAHUB_WEB_URL |
Optional explicit RikkaHub Web base URL |
RIKKAHUB_WEB_PORT |
RikkaHub Web port, default 8080 |
RIKKAHUB_LAST_IP_FILE |
Optional last-successful-IP state file |
RIKKAHUB_HISTORY_RUN_MODE |
stdio or http |
RIKKAHUB_HISTORY_HOST |
MCP bind address, default 0.0.0.0 in HTTP mode |
RIKKAHUB_HISTORY_PORT |
MCP port, default 8766 |
RIKKAHUB_HISTORY_TOKEN |
Bearer token protecting the MCP endpoint |
RIKKAHUB_HISTORY_ALLOWED_HOSTS |
Comma-separated allowed Host headers, e.g. 192.168.0.10:8766 |
RIKKAHUB_HISTORY_ALLOWED_ORIGINS |
Comma-separated allowed Origins |
Start:
.\start_http.ps1
Then configure RikkaHub MCP:
Transport: Streamable HTTP
URL: http://<computer-lan-ip>:8766/mcp
Header: Authorization: Bearer <RIKKAHUB_HISTORY_TOKEN>
RIKKAHUB_HISTORY_ALLOWED_HOSTS must include the host and port used in that URL. DNS rebinding protection remains enabled.
STDIO mode
RIKKAHUB_WEB_PASSWORD=... rikkahub-history-mcp
STDIO is the default when RIKKAHUB_HISTORY_RUN_MODE is not set.
Security
- The MCP tools are read-only.
- Do not commit
start_http.ps1,.env, passwords, JWTs, or Bearer tokens. - Bind to a private LAN only and restrict the port with a host firewall.
- The official RikkaHub Web API itself includes write endpoints; this bridge deliberately exposes none of them.
License
MIT
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。