Skip to content
Agentmart
Submit a tool

Echo Memory

Shared memory for AI agents, as a graph in your own Postgres.

Connector by ayushcodes10 · GitHub account verified by the MCP Registry

IndexedLicense unknownLocal (stdio)Remote (HTTP)★ 2
Write a review

Install

Works with Claude Code, VS Code, Codex, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/ayushcodes10-echo-mem

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

  • https://api.echo-mem.com/mcp Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Shared memory for AI agents, as a graph in your own Postgres. Writes never call an LLM.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
2 read · 3 write · 0 delete · 2 not yet classified
Secrets
2 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Python package

Tools by what they do 7

Read from the source code; the running server may list different tools.

Read 2 · Look things up without changing anything.

  • get_audit_log
  • query_memory

Write 3 · Create, change, send or run things.

  • mark_ingested
  • record_recall_save
  • write_episode

Not yet classified 2 · We could not tell from the name and description.

  • pending_documents
  • trace_cause

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • Authorization
  • ECHO_MEMORY_DATABASE_URL

Other settings (environment variables or headers).

  • ECHO_MEMORY_AGENT_ID
  • ECHO_MEMORY_USER_ID

Network hosts it talks to 1

  • api.echo-mem.com · found in remote endpoint, install command

Files it touches

  • Any path the agent passes to its tools

Tools (7)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • get_audit_log

    Human-readable audit trail: what was written, invalidated, superseded, or resolved, and why. since is an ISO8601 timestamp; entries at or after it, chronologically ordered.

  • mark_ingested

    Close pending documents once their content is in the graph. Pass the same session_id you pass write_episode. Closing a document is one of the two valid answers to a capture prompt - the other is writing the facts - so without it the gate that asked cannot tell a session that complied from one that ignored it. The other half of pending_documents, and it exists because the queue could not be closed by the tool that had just drained it. On 2026-09-12 Codex read a pending note, wrote its facts correctly, and reported: "Its pending marker couldn't be cleared because the local echo-memory command …

  • pending_documents

    Memory files this project has written that are not in the graph yet. A hook notices a file the moment it changes; turning it into entities and facts needs a model, so it waits here for one. Read each path, call write_episode with what it states, then mark_ingested to close it. Claude Code is told about this queue at session start by a hook. Nothing tells any other tool, so this is how they find out at all.

  • query_memory

    Recall prior facts relevant to query, from this agent's own memory (scope="solo") or the pool shared across this user's agents (scope="shared"). Call this at session start, and any other time recalling prior context would save the user from re-explaining something. digest=True ignores query and returns the most recently written active facts, an opt-in "catch me up"; never automatic. as_of (optional): unix seconds. Answers with what this scope believed at that moment, including facts later superseded. Nothing here is ever rewritten, so use it for "what did we think was true when this was deci…

  • record_recall_save

    Record that a fact you recalled from memory saved the user from re-explaining something to you. Call this IN THE SAME TURN, the moment it happens. The trigger is concrete: you called query_memory (or read a memory-derived fact), it answered something the user would otherwise have had to tell you again, and the fact was originally written by a DIFFERENT tool or a past session. That is why this takes only a `fact_id`. Pass the one carried by the query_memory result that helped; the server reads that edge's own agent_id for the writer, and uses its own configured agent id for the reader. You as…

  • trace_cause

    Why something happened, not what resembles it. Follows the causal links recorded on facts about `subject` and returns them as chains, ordered from the subject outwards. Use this when the question is "why", "what did this break", "what was this a consequence of", or "what happens if we undo it". query_memory ranks facts by similarity and returns a flat list, which cannot answer those - the chain is the answer. direction: "upstream" for what led here, "downstream" for what followed, "both" for both. max_hops: 1 to 6, default 3. causes/effects are chains, each a list of facts. contradictions a…

  • write_episode

    Record something worth remembering later: a decision, a correction, a stated preference, or context that would otherwise be re-explained to another tool or a later session. Call it the moment you notice one, not batched and not at the end. You extract the entities and facts; this server never infers. entities: name non-empty, unique within this call type any short string ("tool", "person", "decision") - not an enum facts: source/target must each exactly match a name in entities relation_type any short string ("uses", "decided") - not an enum fact the sentence to re…

Signals

Stars
2
Forks
2
Open issues
1
Weekly downloads
222
Last commit
Oct 22, 2026 (7 days ago)
Last release
Oct 20, 2026 (9 days ago)
Last package publish
Oct 20, 2026 (9 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.ayushcodes10/echo-mem
Version
0.5.3
Auth
Bearer token, API key
Packages
pypi echo-mem
License
License unknown
First seen
Oct 24, 2026
Last checked
Oct 25, 2026
Cite this page

Echo Memory MCP server. Agent Mart. https://agentmart.dev/connectors/ayushcodes10-echo-mem (last updated 2026-10-25)