Provides session capabilities through a typed MCP contract.
Session Memory MCP Server
Policy-controlled access to live and historical agent session context for ADK-Rust Enterprise. Typed session state, scoped memory recall, replay snapshots, and resumable HITL workflows.
What it gives an agent
A purpose-built capability behind one MCP connection.
The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.
Provides memory capabilities through a typed MCP contract.
Architecture
How Session Memory MCP Server fits into an agent system.
The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.
ADK-Rust agent
Chooses a capability from the reviewed tool catalog.
MCP client
Discovers schemas, sends calls, and receives typed content.
Session Memory MCP Server
Validates the request and owns 11 documented tool contracts.
Domain system
Keeps the API, data, credentials, and business rules behind the server.
This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.
Tool catalog
What can an agent ask Session Memory MCP Server to do?
Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.
11 named tools
get_session_stateRead current typed session state
read onlylist_session_eventsInspect trace events, turns, tools, retries, approvals
read onlyretrieve_memorySearch scoped memory for relevant facts
read onlystore_memoryWrite approved memory entries
internal writeupdate_memoryCorrect an existing memory entry (creates new version)
internal writedelete_memoryRemove sensitive or incorrect memory entries
identity security actionredact_memoryRedact PII or sensitive details from memory
internal writelist_memory_refsList memory references that influenced a session
read onlycreate_replay_snapshotFreeze session state for replay
internal writeresume_sessionResume paused HITL workflow
external writeterminate_sessionStop active session with audit reason
external writeGovernance
Understand the effect of every tool.
A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.
- The registry manifest declares read only, internal write, identity security action, external write tool risk classes.
MCP surface
What the current documentation declares.
MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.
Install and connect
Follow the project’s documented starting point.
Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.
cargo install mcp-session-memorylet toolset = McpToolset::from_stdio(
"mcp-session-memory",
["mcp-session-memory"],
).await?;
let agent = LlmAgentBuilder::new("agent")
.tools(toolset.tools().await?)
.build()?;Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.
Official documentation
Continue with the project maintainers’ source of truth.
This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.
Keep exploring
More in business operations.
Source record
Release and repository metadata for this catalog entry.
- Version
- 1.1.0
- License
- Apache-2.0
- Tools
- 11
- Revision
- e041fcce4b74
- Updated
- May 24, 2026