everos-mcp
Enables MCP-compatible coding agents to read and write persistent, Markdown-backed memory via the EverOS REST API.
README
EverOS MCP Server
MCP (Model Context Protocol) server wrapping the EverOS memory runtime API. Lets any MCP-compatible coding agent (Claude Code, Cursor, Codex CLI, Gemini CLI, etc.) read and write persistent, Markdown-backed memory.
How It Works
Coding Agent (MCP client)
│ stdio JSON-RPC
▼
everos-mcp (this package) ──HTTP──▶ EverOS REST API (:8000)
│
Markdown + SQLite + LanceDB
The MCP server is a thin shim. It translates MCP tool calls into EverOS REST API requests and formats responses into LLM-friendly text. No state, no caching — the EverOS server is the single source of truth.
Install
pip install everos-mcp
# or from source:
pip install -e .
Requires Python 3.10+.
Prerequisites
A running EverOS server:
everos server start
# Verify: curl http://localhost:8000/health → {"status":"ok"}
Register with Coding Agents
Claude Code
Add to ~/.claude/mcp.json or <project>/.claude/mcp.json:
{
"mcpServers": {
"everos": {
"command": "python",
"args": ["-m", "everos_mcp.server"],
"env": {
"EVEROS_API_URL": "http://localhost:8000"
}
}
}
}
Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"everos": {
"command": "python",
"args": ["-m", "everos_mcp.server"],
"env": {
"EVEROS_API_URL": "http://localhost:8000"
}
}
}
}
Codex CLI
codex mcp add everos -- python -m everos_mcp.server
Or set EVEROS_API_URL in Codex's MCP env block.
Generic MCP Host
The server uses stdio transport (JSON-RPC 2.0). Configure with:
| Env Var | Default | Description |
|---|---|---|
EVEROS_API_URL |
http://localhost:8000 |
EverOS REST API base URL |
EVEROS_API_KEY |
(none) | Bearer token for authenticated EverOS instances |
MCP Tools
everos_memory_add
Add a message to a memory session. Messages accumulate until flushed.
| Parameter | Required | Description |
|---|---|---|
sender_id |
yes | Who sent the message (e.g., "claude-code", "alice") |
content |
yes | Message content in plain text or Markdown |
session_id |
yes | Session identifier for grouping messages |
role |
no | "user", "assistant", or "tool" (default: "assistant") |
user_id |
no | Owner user ID for scoping |
app_id |
no | App scope (default: "default") |
project_id |
no | Project scope (default: "default") |
timestamp_ms |
no | Unix epoch milliseconds (default: now) |
everos_memory_flush
Force memory extraction and indexing for a session.
| Parameter | Required | Description |
|---|---|---|
session_id |
yes | Session to flush |
app_id |
no | App scope |
project_id |
no | Project scope |
everos_memory_search
Hybrid search (keyword + vector) over stored memories.
| Parameter | Required | Description |
|---|---|---|
query |
yes | Natural language search query |
user_id |
no | Search user-track memories (XOR with agent_id) |
agent_id |
no | Search agent-track memories (XOR with user_id) |
method |
no | "keyword", "vector", "hybrid", or "agentic" (default: "hybrid") |
top_k |
no | Results to return (default: 5, max: 100) |
include_profile |
no | Include user profile in results |
everos_memory_get
Paginated memory listing without ranking.
| Parameter | Required | Description |
|---|---|---|
user_id |
no | Owner user ID (XOR with agent_id) |
agent_id |
no | Owner agent ID (XOR with user_id) |
memory_type |
no | "episode", "profile", "agent_case", or "agent_skill" |
page |
no | Page number (default: 1) |
page_size |
no | Items per page (default: 20, max: 100) |
everos_health
Check EverOS server connectivity. No parameters.
Example Usage (via Claude Code)
Once registered, Claude Code can use these tools directly:
User: "Remember that I prefer pnpm over npm for this project."
Claude calls: everos_memory_add(sender_id="alice", content="Prefers pnpm over npm",
role="user", session_id="<current>")
User (next session): "Set up the package scripts for me."
Claude calls: everos_memory_search(query="package manager preference", user_id="alice")
→ "Prefers pnpm over npm" found — uses pnpm without re-asking
Where Memories Live
All memories are stored as Markdown files in ~/.everos/:
~/.everos/
default/default_project/users/alice/
user.md # user profile
episodes/episode-2026-07-14.md # daily conversation log
You can read, edit, and version-control these files directly.
Development
# Install with dev deps
pip install -e ".[dev]"
# Run tests
pytest src/everos_mcp/tests/ -v
# Manual smoke test (requires running EverOS)
EVEROS_API_URL=http://localhost:8000 python -m everos_mcp.server
License
Apache 2.0 — same as EverOS.
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。