AgentRecall vs Dataecho MCP
A side-by-side look at the AgentRecall and Dataecho MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AgentRecall for knowledge & memory work as a local process; choose Dataecho MCP for knowledge & memory. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AgentRecall when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
session_start, remember, recall.
Choose Dataecho MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You have the keys it needs:
ARTIFACT_API_KEY, ARTIFACT_BASE_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 68/100 · Great | 29/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | ARTIFACT_API_KEYARTIFACT_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 371 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View AgentRecall | View Dataecho MCP |
Tools & capabilities
AgentRecall tools 5
session_startLoads corrections, insights and `watch_for` warnings for the projectrememberSaves one fact; auto-routes to journal / palace room / corrections / awarenessrecallRanked search across every store (RRF), with `useful` feedback that re-weights future rankingcheckMatches the plan against known corrections; returns `verdict: "blocked"` when one overrides itsession_endWrites the journal, promotes insights, records trajectory, optionally opens/closes a pipeline phase
Dataecho MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AgentRecall
{
"mcpServers": {
"goldentrii-agentrecall": {
"command": "npx",
"args": [
"-y",
"agent-recall-mcp"
]
}
}
}
Dataecho MCP
No confirmed install command for Dataecho MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
AgentRecall is categorized under Knowledge & Memory and uses a local stdio subprocess. Dataecho MCP belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick AgentRecall for knowledge & memory work and Dataecho MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Dataecho MCP has no confirmed install command yet — follow its own setup instructions.
AgentRecall is listed as free. Auth: no auth required. Dataecho MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add goldentrii-agentrecall and mcp-9 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AgentRecall has a quality signal of 68/100 (Great) with 5 views, 0 installs and 371 GitHub stars. Dataecho MCP has 29/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.