MCP server registry
Business operationsPublic source

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.

01

Provides session capabilities through a typed MCP contract.

02

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.

01

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

02

MCP client

Discovers schemas, sends calls, and receives typed content.

03

Session Memory MCP Server

Validates the request and owns 11 documented tool contracts.

04

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · streamable HTTP · Server framework: ADK MCP SDK + rmcp

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_state

Read current typed session state

read only
list_session_events

Inspect trace events, turns, tools, retries, approvals

read only
retrieve_memory

Search scoped memory for relevant facts

read only
store_memory

Write approved memory entries

internal write
update_memory

Correct an existing memory entry (creates new version)

internal write
delete_memory

Remove sensitive or incorrect memory entries

identity security action
redact_memory

Redact PII or sensitive details from memory

internal write
list_memory_refs

List memory references that influenced a session

read only
create_replay_snapshot

Freeze session state for replay

internal write
resume_session

Resume paused HITL workflow

external write
terminate_session

Stop active session with audit reason

external write

Governance

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.

4 read only4 internal write2 external write1 identity security action
  • 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.

Prompts
ADK MCP SDKrmcpRegistry manifest

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.

Install
cargo install mcp-session-memory
ADK-Rust connection shape
let 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.

Source record

Release and repository metadata for this catalog entry.

View public repository ↗
Version
1.1.0
License
Apache-2.0
Tools
11
Revision
e041fcce4b74
Updated
May 24, 2026
Transportsstdiostreamable HTTP