recall MCP: what works in Claude, ChatGPT, Cursor, and Grok Bot
Persistent memory for Claude Code and Codex. Search and re-inject context from any session.
Registry name: com.clauderecall/recall (v0.183.2) | npm @clauderecallhq/cli: ? weekly downloads
Status grid
| App | Status | Date tested |
|---|---|---|
| Claude | Untested | Not yet tested |
| ChatGPT | Untested | Not yet tested |
| Cursor | Untested | Not yet tested |
| Grok Bot | Untested | Not yet tested |
| MCP Inspector (reference client) | Untested | Not yet tested |
| MCP TypeScript SDK (reference client) | Untested | Not yet tested |
Hands-on test results
No hands-on tests yet. We do not publish results until we have actually tested.
Automated handshake
No public remote endpoint to check (local or package-only server).
Gotchas
None recorded yet. Gotchas come only from hands-on tests.
Compare with other tested connectors | Connector Weather
Request a hands-on test of recall
Get the badge
Maintain recall or write about it? Show its live ConnectorReport status in your README or docs.
Markdown (README, docs)
[](https://connectorreport.com/c/com-clauderecall-recall?utm_source=badge&utm_medium=embed&utm_campaign=com-clauderecall-recall)
HTML
<a href="https://connectorreport.com/c/com-clauderecall-recall?utm_source=badge&utm_medium=embed&utm_campaign=com-clauderecall-recall"><img src="https://connectorreport.com/badge/com-clauderecall-recall.svg" alt="recall MCP status on ConnectorReport"/></a>
The badge updates on its own after every retest. How badges work