eywa-mcp
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., "@eywa-mcpretrieve handoff from my previous session about MCP routing"
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.
Eywa MCP
Cross-session memory for Claude Code (MCP server + CLI).
The Problem
Claude Code sessions are ephemeral. Context is lost between sessions, so you start fresh each time and re-explain what you were working on.
For heavy Claude Code users with hundreds of sessions, that context reset becomes a major productivity drain.
Related MCP server: agent-mem0
The Solution
Eywa extracts a structured handoff at the end of each session and retrieves relevant past context at the start of the next one.
The name comes from the neural network in Avatar: Eywa connects sessions the way Eywa connects living memory.
How It Works
Eywa runs a deterministic pipeline around your Claude Code transcripts:
Session Detection: 4-strategy fallback (explicit session ID, PID tracing, CWD mtime, global mtime).
Session Conversion: JSONL transcript -> normalized markdown conversation.
Extraction: LLM-powered structured handoff extraction.
Indexing: Inverted index with metadata + TF-IDF-friendly keyword/project maps.
Retrieval: Query keyword scoring + recency decay to return relevant handoffs.
Claude Code JSONL Session
|
v
[Session Detection]
|
v
[JSONL -> Markdown]
|
v
[Structured Extraction]
|
v
[Handoff Markdown + Index]
|
v
eywa_get()Two-Stage Setup
Stage 1: Batch Index (one-time setup)
Use eywa-batch to process existing historical sessions in bulk through OpenRouter.
You can pick any OpenRouter model (Gemini Flash, Claude, GPT, Llama, etc.)
Default batch model:
google/gemini-3-flash-previewDesigned for hundreds of prior sessions
Fast + low-cost extraction pass
Builds your initial handoff corpus and index
Stage 2: Runtime
Run eywa-mcp alongside Claude Code for ongoing sessions.
Uses Claude (Sonnet) extraction at session end (
eywa_extract())Retrieves relevant context at session start (
eywa_get())Installs a companion CLI (
eywa) for scripts and manual use
Installation
Prerequisites
Python 3.10+
Node.js 18+
Claude Code
Option A: Bootstrap (recommended)
Run the repo bootstrap script to check prerequisites and install both Python and Node dependencies:
./setup.shThis installs three commands:
eywa-mcp(MCP stdio server)eywa(CLI: get/extract/rebuild-index)eywa-batch(OpenRouter-powered batch indexing)
Option B: Manual install
1) Install Python package (editable)
pip install -e .2) Install Node extractor dependencies
cd eywa/extractors
npm install
cd ../..3) Configure environment
cp .env.example .env4) Register MCP server
Add to claude_desktop_config.json or ~/.claude.json:
{
"mcpServers": {
"eywa": {
"command": "eywa-mcp"
}
}
}5) Run manually (optional)
eywa-mcpConfiguration
Variable | Default | Description |
|
| Runtime storage root for handoffs and index |
|
| Claude Code session JSONL root |
|
| Tasks directory used for PID-based session detection |
|
| Model used by runtime extraction ( |
|
| OpenRouter model used by batch indexing ( |
| (unset) | OpenRouter API key for batch extraction |
|
| Delay (seconds) between batch API calls |
|
| Concurrent sessions processed by |
|
| Timezone for rendered session timestamps |
|
| Logging verbosity |
Usage
Eywa exposes two MCP tools (for Claude Code) and a CLI (for humans/scripts).
eywa_get()
Retrieve relevant context from prior handoffs.
No query (recent sessions):
{"max_handoffs": 3}With query:
{"query": "mcp tool routing and index scoring", "days_back": 30, "max_handoffs": 4}With tighter options:
{"query": "release pipeline", "days_back": 7, "max_handoffs": 2}Sample output:
## Eywa: 2 past sessions
# Implemented MCP routing fallback logic
## What Happened
- Added explicit tool dispatch guard for unknown tool names.
- Introduced parse-time validation for input payload constraints.
## Open Threads
- Add integration tests for malformed tool inputs.eywa_extract()
Extract and persist a handoff from the active session.
Auto-detect active session:
{}Explicit session ID:
{"session_id": "12345678-1234-1234-1234-123456789abc"}CLI (eywa)
Manual equivalents of the MCP tools:
eywa get # 3 most recent sessions
eywa get "mcp tool routing" --days-back 30 --max 5
eywa extract # auto-detect current session
eywa extract 1b2f6f6b # 8-char short ID
eywa extract 1b2f6f6b-65a6-... # full UUID
eywa rebuild-index # rebuild index from stored handoffsBatch Indexing
Run one-time bulk import of historical sessions:
eywa-batchSet your OpenRouter API key first:
export OPENROUTER_API_KEY=...Choose a model (optional):
export EYWA_OPENROUTER_MODEL=anthropic/claude-3.5-sonnetDry run (no API calls):
eywa-batch --dry-runCustom delay between calls:
eywa-batch --delay 1.0Set concurrency (1-20):
eywa-batch --concurrency 10Limit the run:
eywa-batch --max 50Force reindex all sessions:
eywa-batch --reindexWhat to expect:
Scans
EYWA_SESSIONS_DIRfor*.jsonlSkips already-indexed sessions (unless
--reindex)Skips very short/trivial sessions
Uses OpenRouter Chat Completions with your selected model
Writes handoffs to
YYYY/MM/DD/<session_id>.mdUpdates
handoff-index.jsonincrementallyPrints progress and end-of-run summary
License
MIT. See LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Latest Blog Posts
- 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/buildoak/eywa-continuum'
If you have feedback or need assistance with the MCP directory API, please join our Discord server