Coredence vs Memocall
A side-by-side look at the Coredence and Memocall MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
CoredenceKnowledge & MemoryQuery a measured identity: its rules, the evidence behind each one, and the topics they belong to.36FairAuth: no auth requiredVerdict: choose Coredence for knowledge & memory work; choose Memocall for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Coredence when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: No auth required.
Choose Memocall 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
list_sessions, search_sessions, load_session.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Coredence | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 36/100 · Fair | 60/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Coredence | View Memocall |
Tools & capabilities
Coredence tools
No tool names declared yet. Check the project README from the listing page.
Memocall tools 5
list_sessionsList your recent Claude Code conversations across ALL projects, grouped by project directory. Use this to answer 'what sessions have I worked on recently?' or to find a past session before loading it. Returns each session's title, date, turn count, and id.search_sessionsSearch your past Claude Code conversations (across all projects) by keyword — matches session titles, first messages, and project paths. Use when the user refers to a past conversation by topic (e.g. 'the session where we set up the license system'). Returns matching sessions with their ids.load_sessionLoad the context of a past Claude Code conversation as compact Markdown (human turns, collapsed tool-call summaries, and assistant replies — tool outputs are elided). Provide either a session `id` (from list_sessions/search_sessions) or a free-text `query` to find it. Use this to pull a previous conversation's context into the current session. For a very large session, either pass `turns` to load a specific window (turn numbers come from session_outline), or prefer session_outline / search_in_session.session_outlineGet a quick MAP of a past Claude Code conversation: the numbered list of the user's prompts, one line each. Very cheap even for huge sessions. Use this to see what a session covered, or to find which turn numbers to then load with load_session's `turns`. Identify the session by `id` or free-text `query`.search_in_sessionFind specific turns WITHIN one past Claude Code conversation by keyword — returns only the matching turns (with their turn numbers). Use when the user asks what was decided or discussed about a topic inside a known or large session (e.g. 'what did we decide about retries in that session'). Pick the session by `id` or `session` (free-text); `query` is the keyword to find inside it.
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.
Coredence
No confirmed install command for Coredence yet — follow the setup steps linked from its listing page rather than a guessed package name.
Memocall
{
"mcpServers": {
"baodq06-memocall": {
"command": "npx",
"args": [
"-y",
"memocall"
]
}
}
}
Frequently asked questions
Coredence is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Memocall belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Coredence for knowledge & memory work and Memocall 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. Coredence has no confirmed install command yet — follow its own setup instructions.
Coredence has no declared pricing — check the project's own site. Auth: no auth required. Memocall is listed as free. Auth: no auth required. 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 coredence and baodq06-memocall as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Coredence has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Memocall has 60/100 (Good) with 3 views, 0 installs and 2 GitHub stars.