Acmi Mcp
Give your agent durable memory—profiles, signals, and timelines—backed by Upstash Redis through 16 ACMI MCP tools.
Overview
ACMI MCP is a Build-phase MCP server that provides persistent agent memory via Profile, Signals, and Timeline using 16 tools on Upstash Redis.
What is this MCP server?
- 16 MCP tools for ACMI persistent agent memory
- Profile, Signals, and Timeline memory model for long-running agents
- Upstash Redis REST URL and token required for read-write persistence
- stdio npm @madezmedia/acmi-mcp v1.4.0 plus optional Smithery streamable-http remote
- 16 MCP tools documented in catalog description
- Server version 1.4.0
- npm identifier: @madezmedia/acmi-mcp
Community signal: 3 GitHub stars.
What problem does it solve?
Agents lose user and project context between chats unless you bolt on a real memory store and protocol.
Who is it for?
Solo builders running multi-session agents who already use or can provision Upstash Redis and want structured memory APIs.
Skip if: Builders who need zero external services, only ephemeral chat, or a full managed memory SaaS with no self-hosted Redis.
What do I get? / Deliverables
After configuration, your MCP client can read and write ACMI profiles, signals, and timelines in Upstash Redis across sessions.
- 16-tool ACMI memory surface exposed to your agent
- Redis-backed profiles, signals, and timeline records
- Stdio or remote MCP registration at v1.4.0
Recommended MCP Servers
Journey fit
Persistent memory MCP servers are tagged under Build integrations because they connect your agent stack to external state stores while you develop. Integrations fits Redis-backed memory bridges; Operate monitoring is secondary once the same memory runs in prod.
How it compares
Redis-backed structured agent memory MCP, not a generic vector DB plugin or in-repo documentation skill.
Common Questions / FAQ
Who is ACMI MCP for?
ACMI MCP is for indie developers and agent builders who need durable Profile/Signals/Timeline memory and are comfortable with Upstash Redis credentials.
When should I use ACMI MCP?
Use it during Build when you integrate long-lived agent state, and keep it for Operate when production agents must recall prior signals and timelines.
How do I add ACMI MCP to my agent?
Set UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN, install @madezmedia/acmi-mcp v1.4.0 for stdio or use the Smithery remote URL in your MCP client, then restart.