eywa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EYWA_DATA_DIR | No | Runtime storage root for handoffs and index | ~/.eywa |
| EYWA_TIMEZONE | No | Timezone for rendered session timestamps | UTC |
| EYWA_LOG_LEVEL | No | Logging verbosity | INFO |
| EYWA_TASKS_DIR | No | Tasks directory used for PID-based session detection | <EYWA_SESSIONS_DIR parent>/tasks |
| EYWA_BATCH_DELAY | No | Delay (seconds) between batch API calls | 0.5 |
| EYWA_CLAUDE_MODEL | No | Model used by runtime extraction (eywa_extract) | sonnet |
| EYWA_SESSIONS_DIR | No | Claude Code session JSONL root | ~/.claude/projects |
| OPENROUTER_API_KEY | No | OpenRouter API key for batch extraction | |
| EYWA_OPENROUTER_MODEL | No | OpenRouter model used by batch indexing (eywa-batch) | google/gemini-3-flash-preview |
| EYWA_BATCH_CONCURRENCY | No | Concurrent sessions processed by eywa-batch | 5 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| eywa_getA | Retrieve past session handoffs for context continuity. Called at session start or when you need context about past work.
Examples:
|
| eywa_extractA | Extract a handoff from the current session (or a specified session). Called at end of session to persist a handoff document.
Extracts key decisions, insights, and open threads via the Anthropic Claude model configured by
Examples:
|
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 2 tools
The two tools have clearly distinct purposes: eywa_extract saves a handoff from a session, while eywa_get retrieves past handoffs. There is no functional overlap.
Both tools follow the same pattern: 'eywa_' prefix followed by a descriptive verb (extract, get). This is consistent and predictable.
With only 2 tools, the surface is minimal. While it covers the core extract and retrieve operations for handoffs, it feels thin; additional management tools like delete or list could be expected.
The tools cover the primary operations of creating (extract) and reading (get) handoffs. Gaps include update and delete, but those may not be necessary for immutable handoffs. Minor missing features like listing all handoffs are partially addressed by querying.