MCP.Market

chat-recall MCP server

online · 100% uptime
by munhq·io.github.munhq/chat-recall·v0.7.31·2 stars

One searchable history across every AI coding tool, with secret scanning and a shared task board.

B82/100grade B
What users say
No reviews yet
Be the first
Safety scan
B82/100

not scanned yet

Adoption
Growing

2 stars261 downloads/wk

Reviews

Write one

Nobody has reviewed chat-recall yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

chat-recall tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How chat-recall compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 58% of 1,299 Productivity servers
Uptime
100%
of our recent checks; the typical remote Productivity server answers 100%
Response time
474 ms
faster than 29% of 655 Productivity servers
GitHub stars
2
more than 60% of 854 Productivity servers
Downloads a week
261
more than 75% of 427 Productivity servers with a package

Release history: 16 versions in the registry since 2026-09-16, latest 2026-11-03, typically one every 2 days.

Install chat-recall in Claude Code, Cursor or VS Code

claude mcp add --transport http chat-recall https://chatrecall.dev/mcp
Add to Cursor

What the publisher says

From the chat-recall repository's README, as published. We do not edit it. Read it on GitHub

chatrecall.dev · How it works · MCP tools · Pricing · Self-host · Security

Turn what your AI coding tools already write into shared team knowledge, leaked-secret alerts, ranked code findings and tracked tasks.

Your agents wrote it all down. Nobody read it.

Every coding agent you run keeps a full transcript of its work: the decisions, the reasoning, the keys somebody pasted, the problems it found and never filed. Each one writes to its own directory in its own format, none can read another's, and nothing reads any of them. chat-recall does, through 63 MCP tools.

Underneath all four is one index of every session your tools already wrote, and 28 more tools to search, replay and diff it. That index is the mechanism. It is not the pitch, and it is not why anyone buys this.

The cross-tool part is what makes it work. A single tool's built-in history stops at its own boundary. This does not, and neither does your team.

See it work

Every screen below is real output against a real server, captured from the demo account. Nothing is mocked, replayed or re-timed.

One index, every tool. Search finds a session by what was discussed in it, not by its filename, and memory status shows every source type in one place — sessions beside the skills, MCPs, commands, subagents and hooks that produced them.

Or just ask in plain English — no tool names, no session ids. The agent picks the call itself:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-09-19restoreC → Bscore 82: Shell command built from a string (injection risk)

chat-recall: common questions

Is chat-recall MCP server safe?
Mostly: it is graded B (82/100). Read the chat-recall safety report
How do I install chat-recall?
It runs remotely at chatrecall.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does chat-recall need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is chat-recall maintained?
The last commit was 21 days ago (2026-10-14). The latest release is v0.7.31.
Is chat-recall up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of chat-recall?
Servers from other publishers that do the same job: Joxo MCP server, CLEO MCP Server and Quorus MCP server. Compare all chat-recall alternatives.
How does chat-recall compare with other Productivity MCP servers?
safety score 82/100 (higher than 58% of 1,299 Productivity servers); uptime 100% (of our recent checks; the typical remote Productivity server answers 100%); response time 474 ms (faster than 29% of 655 Productivity servers). Full comparison.

Alternatives to chat-recall

Same job from other publishers: the closest match first, then the best rated.

All chat-recall alternatives →
  • Joxo
    One shared project for a team's coding agents: decisions, a task board and handoffs.
    A
  • CLEO MCP Server
    Task management for AI coding agents — CQRS 2-gateway pattern, 200 ops across 10 domains
    B
  • Quorus
    Shared rooms, messages, file locks and task claims for AI coding agents from any vendor.
    C
  • football-docs
    Searchable football data provider docs for AI coding agents.
    A
  • Argent
    Drive iOS Simulators, Android emulators, TVs and Electron/web apps from your coding agent
    A

More from munhq →