0pi
Give agents free short-lived shared storage to stash context, hand off between workflow steps, or dump intermediate results without building your own Redis.
Overview
io.github.dizzydes/0pi is a MCP server for the Build phase that provides free 2-hour-expiry agent storage to cache context and bridge workflows.
What is this MCP server?
- Free agent storage with 2-hour expiry for caches, workflow bridges, or data dumps.
- npm package @0pi/mcp-server v1.0.3 on stdio transport.
- Configurable OPI_API_URL (default https://0pi.dev) and OPI_LOG_DIR (default ./logs).
- No required API key in published server.json—defaults point at public 0pi.dev endpoint.
- Designed to bridge multi-step agent workflows without long-lived infra.
- Server version 1.0.3; npm identifier @0pi/mcp-server
- Advertised storage expiry: 2 hours
- Default OPI_API_URL: https://0pi.dev
What problem does it solve?
Multi-step agent runs lose context between tools because solo builders lack a zero-setup scratch store with a defined TTL.
Who is it for?
Indie builders prototyping chained agent workflows who need disposable cross-step memory without spinning up paid storage.
Skip if: Production persistence, PII-heavy records, or teams that require guaranteed retention beyond the published 2-hour expiry.
What do I get? / Deliverables
After registering 0pi MCP, agents can read and write short-lived shared blobs via 0pi.dev (or your OPI_API_URL) for about two hours per object.
- MCP tools backed by 0pi short-lived storage (2-hour expiry per product description)
- Configurable remote endpoint defaulting to https://0pi.dev
- Local conversation log directory default ./logs via OPI_LOG_DIR
Recommended MCP Servers
Journey fit
Ephemeral cross-step storage is configured while building agent workflows but also supports ship and operate handoffs, so the canonical shelf remains build/agent-tooling as the integration point. agent-tooling is where MCP servers that extend session memory, bridges, and scratch storage belong in the Skillselion journey.
How it compares
Ephemeral workflow bridge MCP—not a database MCP, secrets manager, or permanent document store.
Common Questions / FAQ
Who is 0pi for?
It is for MCP users who want free, time-bounded storage so agents can cache context or pass data between workflow steps without custom backends.
When should I use 0pi?
Use it while building or iterating multi-step agent flows—especially when you need a quick handoff buffer with automatic expiry after roughly two hours.
How do I add 0pi to my agent?
Install @0pi/mcp-server (v1.0.3), configure stdio MCP in your agent, and optionally set OPI_API_URL (default https://0pi.dev) and OPI_LOG_DIR.