relaycore
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@relaycoreremember that we agreed to deploy on Fridays"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RelayCore
面向本地或自托管 AI runtime 的共享记忆、证据追溯与结构化决策控制面。
中文为主 | English summary below
项目简介
RelayCore 提供一套轻量、可自托管的控制平面,让多个 AI runtime 共享长期记忆、事件时间线、结构化命令流和可追溯决策证据,而不是依赖一次性聊天上下文传话。
当前项目的核心演进方向是:
Shared State:共享 Memory、Command、Event、Mission ControlShared Intelligence:在共享状态之上增加 trace recovery、task canvas、canonical memory、rejected knowledge 和 decision governance
当前仓库公开包含:
SQLite 共享存储
结构化 command bus
append-only event timeline 与 digest
traceable digest、Mermaid task canvas 与 evidence trace refs
MCP-style memory / command tools
Mission Control Web UI
记忆浏览、Trace Inspector、Rejected Knowledge 与冲突处理界面
export、backup、audit、metrics、CORS、token 相关接口
本地历史记忆迁移脚本
核心能力
用统一存储层承载跨 runtime 的长期记忆
用结构化命令总线分发任务、声明权限和记录状态
用事件时间线、digest 和 Mermaid task canvas 追踪执行过程
用
trace_refs/artifact_refs把摘要、决策和记忆反查回原始证据用 memory levels、rejected knowledge 和 decision ledger 沉淀组织知识
用 REST API、CLI、MCP HTTP bridge 与 Web UI 提供多种接入方式
用本地迁移脚本把历史记忆导入 RelayCore
安装
核心服务:
python -m venv .venv
source .venv/bin/activate
pip install -e .[dev]启用 MCP HTTP bridge:
python3.12 -m venv .venv-mcp
source .venv-mcp/bin/activate
pip install -e .[mcp]说明:
核心服务支持
Python 3.9+relaycore mcp-http依赖官方 MCP Python SDK,需要Python 3.10+
快速开始
relaycore init-db
relaycore serve --host 127.0.0.1 --port 8080打开:
http://127.0.0.1:8080/mission-control
也可以直接使用模块入口:
python -m relaycore init-db
python -m relaycore serve --host 127.0.0.1 --port 8080MCP 接入示例
启动 MCP HTTP bridge:
relaycore mcp-http --host 127.0.0.1 --port 9090 --db ~/.relaycore/relaycore.db将示例配置合并到 ~/.codex/config.toml:
[mcp_servers.relaycore]
url = "http://127.0.0.1:9090/mcp"示例文件:
examples/codex/config.toml.example
验证方式:
codex mcp get relaycorecodex mcp list
迁移历史记忆
本地运行现在采用单库约束:
正式运行库只认
relaycore.db如果历史记忆还在旧的
echomemory.db,先做整库并入,再启动服务
整合旧库到正式库:
relaycore consolidate-db --source echomemory.db --target relaycore.db只预览、不写库:
python scripts/migrate_local_memories.py --dry-run显式包含历史摘要和支持的 runtime store:
python scripts/migrate_local_memories.py --dry-run --include-history --include-runtime-store实际导入:
python scripts/migrate_local_memories.py --session-id local-memory-migrationCLI
relaycore init-db
relaycore serve
relaycore export
relaycore mcp-http
relaycore consolidate-db仓库内容
relaycore/:核心运行时代码scripts/:迁移与辅助脚本tests/:自动化测试examples/:公开可用配置示例AGENTS.md/CLAUDE.md:项目级 runtime memory 约束docs/ROADMAP.md:后续规划docs/GITHUB_RELEASE_v1.1.0.md:当前 release 文案
项目级 Memory 约束
如果你希望 Codex、Claude 等 runtime 对这个项目统一走 RelayCore 而不是依赖各自内建 memory,请把下面两份文件作为项目级约束入口:
AGENTS.mdCLAUDE.md
核心原则:
durable project memory 只认 RelayCore
built-in memory 不作为项目记忆源
开始任务先
memory_begin_task读取上下文先
memory_context结束任务前
memory_commit_task
测试
pytest当前本地测试结果(2026-07-22):64 passed
致谢
本项目参考了 EastSword/EchoMemory 的公开项目思路。
许可证
MIT,见 LICENSE。
Overview
RelayCore is a lightweight shared-memory and structured command relay for local or self-hosted AI runtimes.
This public repository includes:
SQLite-backed shared storage
a structured command bus
an append-only event timeline with digests
MCP-style memory and command tools
a Mission Control web UI
a memory viewer and conflict-resolution workflow
export, backup, audit, metrics, CORS, and token-related surfaces
local history migration scripts
Quick Start
relaycore init-db
relaycore serve --host 127.0.0.1 --port 8080Open http://127.0.0.1:8080/mission-control.
MCP Bridge
relaycore mcp-http --host 127.0.0.1 --port 9090 --db ~/.relaycore/relaycore.dbFor Codex, merge the example from examples/codex/config.toml.example into ~/.codex/config.toml.
Validation
pytestLocal status on July 22, 2026:
64 passed
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/totooss/relaycore'
If you have feedback or need assistance with the MCP directory API, please join our Discord server