MCP Agent Toolkit
The MCP Agent Toolkit provides three core reliability patterns for multi-agent AI systems:
Blackboard (Shared Agent State)
blackboard_write— Persist any JSON-serializable artifact (e.g., research briefs, audit reports) scoped by pipeline run and agent nameblackboard_read— Retrieve the latest artifact for a specific run, agent, and key, allowing downstream agents to access upstream outputsblackboard_list— List all artifact keys written by a specific agent in a given run
SCAR Memory (Failure Prevention)
scar_lookup— Check whether a known fix exists for a given error type and agent before retrying (e.g., look up the fix forJSONDecodeError)scar_record— Store a new failure resolution so any agent encountering the same error in the future can retrieve the fix immediately
Response Cache (LLM Cost Reduction)
cache_get— Check whether an identical LLM request (same messages + model) has already been cached, avoiding redundant API callscache_set— Store an LLM response keyed by a SHA-256 hash of the messages and model, so future identical requests are served from cache
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Agent ToolkitSave the final code artifact to the blackboard"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Agent Toolkit
An MCP (Model Context Protocol) server that exposes production agent-kernel tools — blackboard shared state, SCAR failure memory, and LLM response cache — as standard MCP tools any Claude or GPT agent can call.
For project walkthroughs, architecture flowcharts, and system context, visit the live landing page: my-portfolio-github-io-beta-five.vercel.app/projects/mcp-agent-toolkit.html
What it does
Connects the three core reliability patterns from 18 months of building production multi-agent systems into a single MCP server:
Tool Group | Tools | What it solves |
Blackboard |
| Shared agent state without direct coupling |
SCAR Memory |
| Repeated failure prevention — find the known fix before retrying |
Response Cache |
| Stop paying twice for identical LLM requests |
Related MCP server: iranti
Part of The Machine OS
This repo is a spoke of The Machine OS: it
backs the ~~scar-memory and ~~blackboard connectors that supercharge the /debug,
/incident-response, and /agent-design skills.
Prerequisite: Node.js 22.5+ (node:sqlite is built in from 22.5; on recent versions it
runs without a flag and just prints an experimental warning to stderr, which does not affect the
stdio protocol).
Option A — install via the Machine OS plugin (recommended for Claude Code)
/plugin marketplace add shubham0086/the-machine-os
/plugin install ai-engineering-tools@machine-os
/reload-pluginsThis launches the server for you (as the agent-memory MCP server) — no manual config.
Option B — point any MCP client at it directly
Works in Claude Desktop, Cursor, Windsurf, Cline, Zed, or any mcp.json client. No clone needed;
npx fetches and runs it:
{
"mcpServers": {
"agent-memory": {
"command": "npx",
"args": ["-y", "github:shubham0086/mcp-agent-toolkit"],
"env": { "MCP_AGENT_TOOLKIT_DATA_DIR": "/abs/path/to/persist" }
}
}
}MCP_AGENT_TOOLKIT_DATA_DIR is optional but recommended under npx: it points the SQLite store
at a stable path so blackboard state and SCAR memory survive across runs (the npx package dir is
ephemeral). Omit it and storage falls back to the package's own data/ dir.
Local dev
npm install
npm start # runs the stdio server from this checkoutTool reference
Blackboard
blackboard_write(run_id, agent, key, value) — persist an artifact
blackboard_read(run_id, agent, key) — read latest artifact
blackboard_list(run_id, agent) — list all keys for an agentAgents communicate through the blackboard, never directly. The Coder writes code. The Auditor reads code. If either fails and retries, the other's work is still in SQLite.
SCAR Memory
scar_lookup(agent, error_type, context?) — retrieve known resolution
scar_record(agent, error_type, resolution, context?) — store a new resolutionWhen an agent hits JSONDecodeError and you fixed it with json_repair(), record it. Next time any agent hits the same error in the same context, scar_lookup returns the fix before the retry loop starts.
Response Cache
cache_get(messages, model) — check cache before calling LLM
cache_set(messages, model, response, provider) — store response after callSHA-256 hashes the messages + model into a cache key. Identical requests never hit the API twice.
Tests
npm test13 tests covering blackboard isolation, SCAR round-trips, and cache hit/miss behavior.
Stack
MCP SDK (
@modelcontextprotocol/sdk) — the official Anthropic MCP server librarynode:sqlite — Node.js 22 built-in synchronous SQLite, zero native compilation
stdio transport — standard MCP pattern, works with any client
Related repos
agent-scars — standalone SCAR pattern
agent-recall — solution memory
equilibrium — the AgentKernel these patterns came from
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/shubham0086/mcp-agent-toolkit'
If you have feedback or need assistance with the MCP directory API, please join our Discord server