Local-first, auto-injecting, self-aware-about-staleness context + memory layer for coding agents (Claude Code, Codex, MCP). Trust contract
Reporecall MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Local-first, auto-injecting, self-aware-about-staleness context + memory layer for coding agents (Claude Code, Codex, MCP). Trust contract, hooks-first, hybrid retrieval + compression, zero infra.
Reporecall helps Claude Code, Codex, Cline, Aider and other agents work more effectively on large, high-churn or unfamiliar codebases.
Once Reporecall is connected, these are the calls the assistant has available:
Surface — Best userefresh_context — External-tool refresh entry point: re-index code, regenerate wiki/business pages, and return updated statssearch_context — Routed, budgeted, compressed context for the current questionsearch_code — Raw search (action=search) or exact source (action=read_chunk)explain_flow — Navigation: flow / callers / callees / stack_tree / imports / symbol / resolve_seedmemory — recall / explain / list / store / forget (independent of code index)get_stats — Freshness, storage, counts, conventions, latency (use this first when in doubt)Codex — Codex uses Reporecall through the open MCP and CLI surfaces rather than Claude Code hooksBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Reporecall's toolset — Surface, refresh_context, search_context and 5 more — is a fair guide to whether it matches your workflow. It is maintained by proofofwork-agency; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Surface | Best use |
| refresh_context | External-tool refresh entry point: re-index code, regenerate wiki/business pages, and return updated stats. |
| search_context | Routed, budgeted, compressed context for the current question |
| search_code | Raw search (action=search) or exact source (action=read_chunk) |
| explain_flow | Navigation: flow / callers / callees / stack_tree / imports / symbol / resolve_seed |
| memory | recall / explain / list / store / forget (independent of code index) |
| get_stats | Freshness, storage, counts, conventions, latency (use this first when in doubt) |
| Codex | Codex uses Reporecall through the open MCP and CLI surfaces rather than Claude Code hooks. |
{
"mcpServers": {
"reporecall": {
"command": "npx",
"args": ["-y", "@proofofwork-agency/reporecall"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.