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 | |
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/buildoak/eywa-continuum'
If you have feedback or need assistance with the MCP directory API, please join our Discord server