Eion — Shared Memory Server + MCP for Agents

Main

• Bring up storage first: README expects PostgreSQL + Neo4j via docker-compose up -d, plus pgvector enabled.

• Verify health early: hit /health after ./eion-server so you debug infrastructure before wiring MCP clients.

• Use MCP for agent-facing memory ops: README shows connecting via python -m internal.mcp.server with EION_BASE_URL.

• Treat auth fields as mandatory: README says MCP tools require session_id, agent_id, and user_id—register agents before tool calls.

Source-backed notes

• README lists prerequisites: Docker Compose, Go 1.21+, and Python 3.13+.
• README quickstart uses HTTP on http://localhost:8080 with a /health endpoint and a web console at /console/ (trailing slash required).
• README documents MCP configuration in eion.yaml including a default MCP port (8081) and that MCP is embedded in the server process.

FAQ

• Do I need to run a separate MCP daemon?: README says the MCP server is embedded in the Eion server process; clients connect via provided tooling.
• Why does the console URL require a trailing slash?: README explicitly warns to include / for http://localhost:8080/console/.
• How do I authenticate MCP tool calls?: README requires session_id, agent_id, and user_id, and agents must be registered first.