madezmedia avatar

Acmi Mcp

madezmedia/acmi

If you're building agents that need to remember things across conversations, this gives you 16 tools for persistent context on Upstash Redis. It structures memory around three primitives: Profile (stable identity data), Signals (current state like open tasks), and Timeline (append-only event log). Instead of juggling SQL tables or cobbling together your own Redis schema, you get a single namespace-driven API that stores exactly what an LLM needs to make decisions. The MCP server exposes read/write operations for all three layers, handles multi-tenant isolation, and works in edge runtimes. Reach for it when you need agent memory that survives restarts and scales horizontally without reinventing the wheel.

GitHub stars
3
tools
17
auth
Secret needed
transport
STDIO, HTTP
env vars
2
last updated
May 14, 2026

Tools

17 tools

Public tool metadata for what this MCP can expose to an agent.

acmi_profileCreate or update an entity profile in ACMI. Stores arbitrary JSON profile data for an entity (agent, thread, project, etc.).3 params

Create or update an entity profile in ACMI. Stores arbitrary JSON profile data for an entity (agent, thread, project, etc.).

Parameters* required
idstring
Entity ID within the namespace
namespacestring
ACMI namespace (e.g. 'agent', 'thread', 'sales')
profilestring
JSON string of profile data to store
acmi_signalUpdate AI signals for an entity. Signals are mutable KV state (mood, priorities, scores, etc.) that changes frequently.3 params

Update AI signals for an entity. Signals are mutable KV state (mood, priorities, scores, etc.) that changes frequently.

Parameters* required
idstring
Entity ID
namespacestring
ACMI namespace
signalsstring
JSON string of signal data to store
acmi_eventLog a timeline event for an entity. The workhorse tool — records timestamped events with source, kind, correlationId, and summary. Follows ACMI Communication Standard v1.1.6 params

Log a timeline event for an entity. The workhorse tool — records timestamped events with source, kind, correlationId, and summary. Follows ACMI Communication Standard v1.1.

Parameters* required
correlationIdstring
Correlation ID for tracking across agents/sessions (camelCase)
idstring
Entity ID
kindstring
Event kind (e.g. 'handoff-complete', 'step-done', 'decision')
namespacestring
ACMI namespace (e.g. 'thread', 'agent', 'work')
sourcestring
Source of the event (agent name, system, etc.)
summarystring
Human-readable event summary
acmi_getFetch complete entity context: profile + signals + recent timeline events (last 10).2 params

Fetch complete entity context: profile + signals + recent timeline events (last 10).

Parameters* required
idstring
Entity ID
namespacestring
ACMI namespace
acmi_listList all entity IDs in a namespace.1 params

List all entity IDs in a namespace.

Parameters* required
namespacestring
ACMI namespace to list
acmi_work_createCreate a new work item (cross-session project, task, or idea).2 params

Create a new work item (cross-session project, task, or idea).

Parameters* required
idstring
Unique work item ID
profilestring
JSON string of work item profile (title, owner, status, etc.)
acmi_work_eventLog a progress event on a work item.4 params

Log a progress event on a work item.

Parameters* required
idstring
Work item ID
sessionIdstring
Optional session ID to associate
sourcestring
Source of the event
summarystring
Event summary
acmi_work_signalUpdate signals for a work item (progress, blockers, metrics, etc.).2 params

Update signals for a work item (progress, blockers, metrics, etc.).

Parameters* required
idstring
Work item ID
signalsstring
JSON string of signal data
acmi_work_getRead a work item's full context: profile, signals, timeline (last 50), and sessions.1 params

Read a work item's full context: profile, signals, timeline (last 50), and sessions.

Parameters* required
idstring
Work item ID
acmi_work_listList all work item IDs.

List all work item IDs.

No parameter schema in public metadata yet.

acmi_catMulti-stream event merge view. Combines timeline events from multiple entities, sorted by timestamp. Supports --since filtering.3 params

Multi-stream event merge view. Combines timeline events from multiple entities, sorted by timestamp. Supports --since filtering.

Parameters* required
keysarray
Timeline keys to merge. Use 'thread:name', 'agent:name', or full 'acmi:...:timeline' keys.
limitnumber
Max events to return. Default: 50.
sincestring
Time window filter (e.g. '24h', '7d', '30m'). Default: all time.
acmi_spawnLog an agent session spawn event. Records when an agent starts a new session.3 params

Log an agent session spawn event. Records when an agent starts a new session.

Parameters* required
agentIdstring
Agent ID that spawned
modelIdstring
Model ID used for the session
sessionIdstring
Session ID
acmi_bootstrapOne-shot agent context bundle. Fetches everything a fresh agent session needs: profile, signals, active threads, rollup, recent timeline, and spawns.1 params

One-shot agent context bundle. Fetches everything a fresh agent session needs: profile, signals, active threads, rollup, recent timeline, and spawns.

Parameters* required
agentIdstring
Agent ID to bootstrap
acmi_activeTrack agent thread engagement. Add/remove threads or list current active threads for an agent.4 params

Track agent thread engagement. Add/remove threads or list current active threads for an agent.

Parameters* required
actionstring
Action: add a thread, remove a thread, or list all active threadsone of add · remove · list
agentIdstring
Agent ID
rolestring
Role in thread (e.g. 'participant', 'lead'). Default: 'participant'
threadKeystring
Thread key (required for add/remove)
acmi_rollup_setSet the latest rollup snapshot for an agent (acmi:agent:<id>:rollup:latest). Pairs with acmi_bootstrap which reads it.2 params

Set the latest rollup snapshot for an agent (acmi:agent:<id>:rollup:latest). Pairs with acmi_bootstrap which reads it.

Parameters* required
agentIdstring
Agent ID
rollupstring
JSON string of rollup data (cross-session summary, decisions, blockers, etc.)
acmi_deleteDelete an ACMI key. Refuses protected paths (acmi:registry:*, acmi:notion-sync:*) and any non-acmi:* key. Defaults to dry-run; pass confirm=true to actually delete.2 params

Delete an ACMI key. Refuses protected paths (acmi:registry:*, acmi:notion-sync:*) and any non-acmi:* key. Defaults to dry-run; pass confirm=true to actually delete.

Parameters* required
confirmboolean
Must be true to actually delete; otherwise returns dry-run preview. Default: false (dry-run).
keystring
Full ACMI key to delete (must start with 'acmi:')
acmi_search_semanticPerform semantic search across fleet coordination history. Finds relevant past events, decisions, and work items based on natural language queries. Returns original ACMI correlationIds for linking.2 params

Perform semantic search across fleet coordination history. Finds relevant past events, decisions, and work items based on natural language queries. Returns original ACMI correlationIds for linking.

Parameters* required
limitnumber
Number of results to return. Default: 5.
querystring
Natural language search query (e.g. 'previous decisions about SSE timeouts')

Sponsors

Configuration

UPSTASH_REDIS_REST_URL*

Upstash Redis REST URL (https://your-instance.upstash.io)

UPSTASH_REDIS_REST_TOKEN*secret

Upstash Redis REST token (read-write)

Readme

ACMI v1.5 banner

ACMI - Agentic Context Memory Interface

npm Protocol v1.5 MCP v1.5.0 License: MIT Node.js Conformance: 36/36

The coordination backbone for AI agent fleets. Three Redis keys - Profile, Signals, Timeline.

ACMI is the open protocol for persistent agent context. Version v1.5 formalizes Fleet Comms Protocol: atomic pre/post events, wake-directives, handoff-ack chains, and correlation-aware timelines that make multi-agent work auditable instead of anecdotal.

Every entity stores exactly three things an LLM needs to make decisions:


View the full README on GitHub

Details

Repository
github.com/madezmedia/acmi
Categories
Databases, AI & LLM Tools
Package
@madezmedia/acmi-mcp
Transport
STDIO, HTTP
Auth
Required
Registry
MCP registry, active

Related Databases MCP servers

View all
1nikitacometa avatarMnemon Mcpnikitacometa/mnemon-mcpPersistent layered memory for AI agents. SQLite FTS5, fact versioning, zero-cloud.3stars
2agentic-eng avatarA2dbagentic-eng/a2dbSafe, read-only database access for AI agents. 5 databases, batch queries, SQLGlot.2stars
3lu-zhengda avatarVirtual Filesystemlu-zhengda/mcp-virtual-fsPostgreSQL-backed virtual filesystem for agents: session isolation, shared stores, POSIX ops, RLS.2stars
4shrike-security avatarShrikeshrike-security/shrike-mcpGoverns what AI agents do: tool calls, SQL, commands, files checked against policy before they run.2stars
5alyiox avatarClickHousealyiox/mcp-clickhousexRead-only MCP server for ClickHouse metadata, parameterized queries, and plan analysis.1stars
6arpe-io avatarFastbcp Mcparpe-io/fastbcp-mcpMCP server for FastBCP — high-performance parallel database export to files and cloud1stars