What can you do with this server?

The EGC server provides persistent AI memory management across coding sessions and tools, allowing AI assistants to remember project context, decisions, and preferences across sessions. * get_state: Retrieve full project memory at session start, including past decisions, preferences, things to avoid, and next steps — scoped per project path. * update_state: Save and merge session decisions, preferences, next steps, and avoidances at session end. Non-destructive — merges with existing memory without erasing history. * store_decision: Persist a specific decision with its context into SQLite storage, with a lock arbitration mechanism to prevent conflicts. * query_history: Retrieve past decisions with pagination support (limit/offset) to review historical choices across sessions. * get_project_state: Retrieve the current project state snapshot (alternate/lighter state retrieval). Key behaviors: * Memory is stored locally (~/.egc/state/) as Markdown files backed by SQLite. * State is scoped per project path, so different projects maintain independent memory. * Designed to be called automatically at session start (get_state) and end (update_state).

Which integrations are available for this server?

Allows Amp to use EGC's memory protocol for persistent context across sessions. Allows Obsidian vault access to AI tools via MCP, enabling reading, searching, and writing notes.

EGC

by Fmarzochi

Overview Schema Related Servers Score Discussions

JavaScript

Local

npm version Node.js >= 20 TypeScript Discord PRs Welcome Stars Forks Issues Maintained OpenSSF Scorecard Quality Gate Security Rating Reliability Rating Socket EGC MCP server Featured on Product Hunt

Language / اللغة / Idioma / भाषा / 언어 / Язык

EGC - Extended Global Context

Your AI agents never start from zero again.

No commands to learn. Just work - EGC handles the rest.

EGC is a local runtime that gives every AI coding tool you use a persistent memory. At the end of each session, your AI saves what it learned: decisions made, what failed, your preferences, what to pick up next. At the start of the next session, it loads that state back on its own - no prompting required. Say "let's continue" or "where did we stop?" in any language and your AI already knows what to do. One install covers Claude Code, Cursor, Gemini CLI, Windsurf, and more. Works with Claude, GPT-4o, Gemini, and OpenRouter models including DeepSeek, Qwen3, and Llama 4.

This is what EGC looks like in practice

You open Claude Code on a project you haven't touched in two weeks. Without typing anything:

State loaded from egc-memory via ~/.egc/state/Projects-MyApp.md

Context and preferences acknowledged (terse responses).

Ready to pick up the next items:
• Test full install on a clean machine
• Add GEMINI.md with session memory protocol
• Publish v1.0.1 fix to npm after clean install test passes
• Add mcp_server_count to audit.js

=== EGC Stack Briefing ===
Stack: typescript, javascript
Stack agents: typescript-reviewer, javascript-reviewer
Always use: code-reviewer
Skill: coding-standards (cyclomatic complexity) - apply to all code written this session
===

The AI already knows what you were building, what decisions you made, what failed, and exactly where you stopped. It knows because EGC saved that state at the end of your last session and loaded it back when this one started - on its own, without you asking. You didn't type anything. You just started working.

Related MCP server: Total Recall

Install

npm install -g @egchq/egc && egc install

Or run without installing globally:

npx @egchq/egc install

Full installation guide

What EGC gives your AI

EGC ships two MCP servers that work together during every session.

Memory - 14 tools that your AI uses automatically

No commands to memorize. Your AI reads this table so you never have to. Say anything in any language - "continue from yesterday", "remember this decision", "what broke last time?" - and it calls the right tool. You just work. EGC handles the rest.

egc-memory

Tool	What it does
`get_state`	Loads project memory at session start
`update_state`	Saves decisions, preferences, and next steps
`store_decision`	Persists a single decision to SQLite
`query_history`	Returns past decisions by timestamp
`search_history`	Full-text search with BM25 ranking
`working_memory_set`	Stores transient context with a TTL
`working_memory_get`	Reads a transient key
`working_memory_list`	Lists all live transient entries for the current project
`lesson_save`	Records cross-session knowledge with confidence decay
`lesson_recall`	Retrieves active lessons above a confidence threshold
`lesson_reinforce`	Boosts confidence on a lesson when the same pattern repeats
`detect_patterns`	Surfaces repeated commands and recurring errors from hook events
`compress_observations`	Compresses raw hook observations into typed summaries to reduce token usage
`get_project_state`	Returns server health metadata and storage engine status

State files live at ~/.egc/state/<project-slug>.md. One file per project, plain Markdown, human-readable.

Context and safety - 5 tools for when things get heavy

egc-guardian

These tools run automatically in the background. Every shell command and every file write is checked before it executes. You never invoke them directly.

Tool	What it does
`validate_command`	Checks shell commands against project safety rules before execution
`validate_write`	Validates file write paths to prevent unsafe writes
`reduce_context`	Compresses file payloads to save your token budget
`orchestrate_task`	Routes prompts with agent/skill context and returns compression metrics
`auto_learn`	Mines session failures and writes actionable lessons to all AI tool config files in the project

Always in sync - across every tool you use

egc watch - run it once and every tool you use stays in sync. Edit context in Cursor and it appears in Gemini CLI, Copilot, Windsurf, and everywhere else automatically. When your state updates, all your tool config files update with it. No manual steps, no stale state.

egc watch              # watch current project
egc watch /path/proj   # watch a specific project
egc watch --quiet      # suppress output

Dashboard - real-time Mission Control

See every tool call, token, and cost your agents generate -- live in your browser. Starts automatically after egc init. Full guide

Prompt library

479 components included as a bonus. Install to get access to 63 agents, 229 skills, and 76 commands, plus 111 rules, all written from real engineering sessions. Skip them entirely and EGC still gives you persistent memory.

Support EGC

EGC is built by one developer, maintained in the open, and free.

Website: full docs, feature overview, and live demo
Join the Discord: ask questions, share feedback
Sponsor on GitHub: any amount
Donate via PayPal: no GitHub account needed
Star the repository: helps other developers find it
Contribute: agents, skills, commands, bug fixes, docs
Share: if EGC changed how you work, tell someone

Latest Blog Posts

Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp

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/Fmarzochi/EGC'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

EGC

EGC - Extended Global Context

This is what EGC looks like in practice

Install

What EGC gives your AI

Memory - 14 tools that your AI uses automatically

Context and safety - 5 tools for when things get heavy

Always in sync - across every tool you use

Dashboard - real-time Mission Control

Prompt library

Support EGC

Sponsors

Tool Partners

Annual Sponsors · Be the first annual sponsor.

Backers

Monthly sponsors · be the first

Maintenance

Resources

Tools

Latest Blog Posts

MCP directory API