Statelessagent MCP Server

SAME gives every AI coding tool persistent memory. Claude Code, Cursor, Windsurf, Codex CLI, Gemini CLI — one memory layer that works everywhere. It

Local serverstdioPython

What is the Statelessagent MCP server?

Statelessagent MCP server exists for a simple reason — assistants are far more useful when they can act on Statelessagent directly instead of describing what you should do. SAME gives every AI coding tool persistent memory. Claude Code, Cursor, Windsurf, Codex CLI, Gemini CLI — one memory layer that works everywhere. It indexes your markdown notes, surfaces relevant context automatically, and records.

What you get

  • Your AI remembers everything — -- Decisions, handoffs, and context survive across sessions. Close your terminal, switch projects, come back tomorrow. Nothing gets lost
  • Memory integrity — -- Tracks provenance (where notes came from), detects when source files change, and flags stale knowledge. Stale notes rank lower in search automatically. same health shows trust state across your vault
  • Dual-layer memory — -- Extracts atomic facts from your notes via LLM. Facts are independently searchable and boost source notes in search results. The right answer surfaces even when the fact is buried in an unrelated conversation
  • Streamable HTTP transport — -- same web --mcp enables an HTTP MCP endpoint with Bearer token auth. Connect from Open WebUI, LobeChat, or any HTTP MCP client — no stdio required
  • Works with your tools — -- 19 MCP tools for Claude Code, Cursor, Windsurf, or any MCP client. Search, save decisions, create handoffs without leaving your editor
  • Safe for teams — -- Multiple AI agents on the same codebase won't step on each other. File claims, push protection, and attribution built in

Setting it up

The server ships on npm as same, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Statelessagent is connected, these are the calls the assistant has available:

  • Dual — layer memory** -- Extracts atomic facts from your notes via LLM. Facts are independently searchable and boost source notes in search results. The
  • Metric — Value
  • MRR0.65 keyword, 0.62 semantic
  • search_notes — Semantic search across your knowledge base
  • search_notes_filtered — Search with domain/tag/agent filters
  • search_across_vaults — Federated search across multiple vaults
  • get_note — Read full note content by path
  • find_similar_notes — Discover related notes
  • get_session_context — Pinned notes + latest handoff + git state
  • recent_activity — Recently modified notes
  • save_note — Create or update a note
  • save_decision — Log a structured project decision

Configuration and credentials

You will need one environment variable: VAULT_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Statelessagent.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the statelessagent mcp server does with a few real requests.

Choosing this one

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Statelessagent's toolset — Dual, Metric, MRR and 11 more — is a fair guide to whether it matches your workflow. It is maintained by sgx-labs; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Statelessagent's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
Duallayer memory** -- Extracts atomic facts from your notes via LLM. Facts are independently searchable and boost source notes in search results. The right answer surfaces even when the fact is buried in an unrelated convers
MetricValue
MRR**0.65** keyword, **0.62** semantic
search_notesSemantic search across your knowledge base
search_notes_filteredSearch with domain/tag/agent filters
search_across_vaultsFederated search across multiple vaults
get_noteRead full note content by path
find_similar_notesDiscover related notes
get_session_contextPinned notes + latest handoff + git state
recent_activityRecently modified notes
save_noteCreate or update a note
save_decisionLog a structured project decision
create_handoffWrite a session handoff
reindexRe-scan and re-index the vault

How to install the Statelessagent MCP server

{
  "mcpServers": {
    "statelessagent": {
      "command": "npx",
      "args": ["-y", "same"],
      "env": {
        "VAULT_PATH": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
VAULT_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Statelessagent to Dual.
  • Use Statelessagent to Metric.
  • Use Statelessagent to MRR.

Frequently asked questions

It connects Statelessagent to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Dual, Metric, MRR, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Statelessagent directly.