Features / MCP Server

Your AI remembers

The MCP server lets AI agents search your past sessions and read project context during conversations. One command to install.

mcp install
$ sfs mcp install --for claude-code
MCP server configured for Claude Code.
Restart Claude Code to activate.
22 tools available to your AI agent:
Session tools (7):
• search_sessions — Search past sessions
• get_session_context — Full conversation from a session
• list_recent_sessions — Browse recent work
• find_related_sessions — Find by file or error
• get_session_summary — Structured session summary
• get_audit_report — Trust audit report
• get_session_provenance — Which rules instructed a session
Knowledge read (8):
• get_project_context — Full wiki: overview + pages + concepts
• get_context_section — One section of the context doc
• get_wiki_page — One wiki page in full
• search_project_knowledge — Search knowledge entries
• list_knowledge_entries — Filter by type / class / freshness
• get_knowledge_entry — One entry's full record
• get_knowledge_health — Pending / compiled counts
• ask_project — Q&A against knowledge base
Knowledge write (5):
• add_knowledge — Save a discovery / decision / pattern
• update_wiki_page — Create or update a wiki page
• list_wiki_pages — Browse wiki structure
• compile_knowledge_base — Trigger a compile pass
• dismiss_knowledge_entry — Dismiss a stale or wrong entry (audited)
Rules (2):
• get_rules — Canonical project rules
• get_compiled_rules — Compiled rules per tool

What the MCP server gives you

One-command install

Works with Claude Code, Cursor, and Copilot. Adds SessionFS to your tool's MCP config file automatically — no manual JSON editing.

Project context

Share architecture decisions, coding conventions, and API contracts with every AI agent on your team. One document per repo, always current.

Local + Remote

Local MCP server on stdio for desktop tools — no network required. Remote HTTP/SSE server for cloud-connected AI tools and team sharing.

How agents use session memory

When you start a new session, your AI agent can automatically search for related past sessions and load their context — so it already knows what you tried last time.

The find_related_sessions tool maps file paths and error strings to previous sessions. If you're debugging the same file you touched last week, the agent knows.

Read the MCP docs
agent using MCP
Agent calls MCP tool
find_related_sessions ("tokens.py")
SessionFS returns
ses_abc — Debug auth middleware (2 days ago)
ses_d2e — JWT token refresh fix (5 days ago)
Agent says
"I found 2 related sessions. The last time you worked on tokens.py, you extended the expiry window and added redis for caching..."