What fields does a capsule contain?
A capsule always includes a `summary` (≤500 chars), and optionally `decisions` (up to 20 strings), `next_steps` (up to 20 strings), a `payload` (up to 32KB JSON), and `refs` (workflow/agent/session IDs).
@Johnny-Z13
Basic information
Portable context for agent workflows — structured handoff packets for AI agents
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"contextcapsule": {
"command": "npx",
"args": [
"-y",
"@contextcapsule/mcp-server"
],
"env": {
"CONTEXTCAPSULE_API_KEY": "ak_your_key_here"
}
}
}
}Create a Context Capsule to hand off execution context between agents or sessions. Include a summary of what happened, key decisions made, and what should happen next. Capsules are structured, compressed, ephemeral context packets. Returns a capsule_id and capsule_url. Capsules expire after 7 days by default.
Fetch a Context Capsule to resume work from where another agent left off. Returns the full capsule data: summary, decisions, next_steps, payload, and refs. Use this to pick up execution context from a previous session or agent. No API key required.
Get a free Context Capsule API key. Returns the key directly — save it immediately, it cannot be retrieved later. Only needed once. After signup, configure the key as CONTEXTCAPSULE_API_KEY environment variable to use create_capsule. Free tier: 500 capsules per month.
Context Capsule is a portable execution context for agent workflows. It packages structured, compressed, ephemeral context (facts, state, next-step intent) that travels between agents, sessions, and tools, so agents can resume where they left off instead of restarting.
Get an API key via POST /v1/auth/signup, then create a capsule with POST /v1/capsules and fetch it with GET /v1/capsules/:id. Alternatively, use the MCP server by running npx -y @contextcapsule/mcp-server and configuring it in any MCP-compatible client (e.g., Claude Desktop) with your API key.
expires_in).idempotency_key to prevent duplicates on retry.create_capsule and fetch_capsule tools.A capsule always includes a `summary` (≤500 chars), and optionally `decisions` (up to 20 strings), `next_steps` (up to 20 strings), a `payload` (up to 32KB JSON), and `refs` (workflow/agent/session IDs).
By default 7 days. You can set `expires_in` to any value between 60 and 604800 seconds. Expired capsules are automatically cleaned up.
Create an API key via `POST /v1/auth/signup` (save the returned key immediately). Use that key as a Bearer token in the `Authorization` header for create requests. Fetching capsules does not require auth.
Yes. Requirements: Node.js 18+, PostgreSQL. Clone the repo, copy `.env.example`, set `DATABASE_URL` and `BASE_URL`, run migrations, seed an API key, then start with `npm run dev`.
Create capsule: 60 requests per minute per API key. Fetch capsule: 120 requests per minute per IP. Signup: 5 requests per minute per IP.

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi
Open-source MCP to use Blender with any LLM
MCP Toolbox for Databases is an open source MCP server for databases.

Health by Dr Brad works out a health plan from your own results: which screening is due at your age, and evidence-based suggestions, each with the reason and the published guideline or study behind it. Your record is one
Hindsight: Agent Memory That Learns
Comments