Context Capsule
@Johnny-Z13
Context Capsule について
Portable context for agent workflows — structured handoff packets for AI agents
基本情報
設定
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"contextcapsule": {
"command": "npx",
"args": [
"-y",
"@contextcapsule/mcp-server"
],
"env": {
"CONTEXTCAPSULE_API_KEY": "ak_your_key_here"
}
}
}
}ツール
ツールは検出されませんでした
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
概要
What is Context Capsule?
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.
How to use Context Capsule?
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.
Key features of Context Capsule
- Structured context packet with summary, decisions, next steps, payload, and refs.
- Capsules auto-expire after 7 days (configurable via
expires_in). - Idempotent creation with
idempotency_keyto prevent duplicates on retry. - MCP server provides
create_capsuleandfetch_capsuletools. - Rate-limited endpoints (60 create/min per key, 120 fetch/min per IP).
- Self-hostable with Node.js 18+, PostgreSQL, and Vercel/Neon stack.
Use cases of Context Capsule
- Handoff between two agents in a multi-agent workflow (e.g., schema migration to testing).
- Resume a long-running task after a session interrupt.
- Pass execution context between different tools or services in a pipeline.
- Replace manual prompt summarization with a machine‑readable capsule.
FAQ from Context Capsule
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).
How long does a capsule live?
By default 7 days. You can set expires_in to any value between 60 and 604800 seconds. Expired capsules are automatically cleaned up.
How do I authenticate?
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.
Can I self-host Context Capsule?
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.
What are the rate limits?
Create capsule: 60 requests per minute per API key. Fetch capsule: 120 requests per minute per IP. Signup: 5 requests per minute per IP.
「その他」の他のコンテンツ
ghidraMCP
LaurieWiredMCP Server for Ghidra
MCP Toolbox for Databases
googleapisMCP Toolbox for Databases is an open source MCP server for databases.
MCP Go 🚀
mark3labsA Go implementation of the Model Context Protocol (MCP), enabling seamless integration between LLM applications and external data sources and tools.
Awesome Mcp Servers
punkpeyeA collection of MCP servers.
Reactive Resume
amruthpillaiA one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
コメント