everos-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVEROS_URL | No | Local EverOS URL (default: http://127.0.0.1:8000) | http://127.0.0.1:8000 |
| EVEROS_APP_ID | No | App/source id (default: claude-code) | claude-code |
| EVEROS_USER_ID | No | User id (default: $USER) | $USER |
| EVEROS_AGENT_ID | No | Assistant id (default: claude) | claude |
| EVEROS_PROJECT_ID | No | Pin a project_id instead of deriving from cwd (optional) | |
| EVEROS_MCP_AUTOSTART | No | Auto-start EverOS via everos-up if down (default: 1) | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_memoryA | Search your local EverOS memory — past Claude Code conversations you
ingested (via everos-ingest-claude) or facts you saved with |
| rememberA | Store a fact / decision / note into local EverOS memory for later recall.
Use for high-value context worth keeping across sessions (architecture
decisions, preferences, key findings) — not whole conversations. Scoped to
the current project unless |
| briefingA | Session-start briefing: your most recent episodes + profile for the current project. Call at the start of a session to recall recent work. |
| list_memoriesA | Paginate through your local EverOS memories by type. memory_type: episode | profile | agent_case | agent_skill. episode/profile are user-scoped; agent_case/agent_skill are agent-scoped (uses the configured agent_id). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: briefing for session summary, list_memories for paginating memories by type, remember for storing new facts, and search_memory for querying. No overlap or ambiguity.
Three tools follow a verb_noun pattern (list_memories, remember, search_memory), but 'briefing' is a noun command, breaking the pattern. Otherwise consistent.
Four tools cover the essential memory operations (ingest, list, store, search) without being too few or excessive, well-scoped for the server's purpose.
The set supports create (remember) and read (list_memories, search_memory, briefing) but lacks update and delete operations, leaving a significant gap for full CRUD lifecycle.