cachebro

cachebro provides a local file cache for AI coding agents. It stores file versions in an embedded Turso/SQLite-compatible database, hashes file contents to detect changes, and returns either full content (first read), an 'unchanged' response, a unified diff for updated files, or partial unchanged/updated ranges for offset/limit reads. It can be run as a CLI that exposes an MCP server with caching tools, or used as a TypeScript SDK.

Evaluated Mar 30, 2026 (21d ago)
Repo ↗ DevTools mcp cache diff tokens ai-coding-agents typescript turso local-first
⚙ Agent Friendliness
63
/ 100
Can an agent use this?
🔒 Security
27
/ 100
Is it safe for agents?
⚡ Reliability
31
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
80
Documentation
75
Error Messages
0
Auth Simplicity
95
Rate Limits
0

🔒 Security

TLS Enforcement
0
Auth Strength
20
Scope Granularity
0
Dep. Hygiene
55
Secret Handling
70

Local-first design with no described auth suggests reduced risk of external exposure, but increases reliance on local environment security. The cache persists file contents/diffs locally in an embedded database; this can be sensitive. No information is provided on transport security (TLS) for the MCP server, access controls, or how inputs/paths are validated.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
35
Error Recovery
45
AF Security Reliability

Best When

Single-user (or locally isolated) agent workflows where repeated reads of the same local files occur during multi-step coding tasks.

Avoid When

When you need rigorous security boundaries between different users/projects, or when local disk persistence of cached file data is not acceptable.

Use Cases

  • Reducing LLM token usage by avoiding repeated full-file reads
  • Providing compact diffs to agents during iterative coding/refactoring
  • Accelerating agent workflows in local editor integrations via MCP tooling
  • Tracking per-session read state to avoid redundant reads across a coding session

Not For

  • Production multi-tenant SaaS scenarios where multiple users need strong isolation and authentication
  • Use cases requiring remote file access across networks or centralized cache management
  • Environments that cannot allow local file hashing/caching of repository contents

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication described. The MCP server appears intended for local use within a user's editor/agent environment.

Pricing

Free tier: No
Requires CC: No

Open-source (MIT) and distributed via npm; no pricing model described.

Agent Metadata

Pagination
offset/limit supported for partial reads; no mention of cursor-based pagination.
Idempotent
True
Retry Guidance
Not documented

Known Gotchas

  • If the underlying MCP server is not configured/enabled, the agent may fall back to built-in file reading tools.
  • The cache relies on file content hashing; large files or high churn may reduce savings.
  • Partial reads depend on offset/limit; if agents request different ranges each time, benefits may be smaller.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for cachebro.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered