Synap Memory vs Central Intelligence
A side-by-side look at the Synap Memory and Central Intelligence MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Synap Memory for knowledge & memory work as a local process; choose Central Intelligence 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?
Choose Synap Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Choose Central Intelligence when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CI_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 44/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | CI_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 77 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Synap Memory | View Central Intelligence |
Tools & capabilities
Synap Memory tools
No tool names declared yet. Check the project README from the listing page.
Central Intelligence 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.
Synap Memory
{
"mcpServers": {
"synap-memory": {
"command": "uvx",
"args": [
"maximem-synap"
]
}
}
}
Central Intelligence
{
"mcpServers": {
"alekseimarchenko-central-intelligence": {
"command": "npx",
"args": [
"-y",
"central-intelligence-local"
],
"env": {
"CI_API_KEY": "YOUR_CI_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Synap Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Central Intelligence belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Synap Memory for knowledge & memory work and Central Intelligence 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.
Synap Memory has no declared pricing — check the project's own site. Central Intelligence is listed as freemium — a free tier with paid plans. Auth: api key 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 synap-memory and alekseimarchenko-central-intelligence as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Synap Memory has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 77 GitHub stars. Central Intelligence has 51/100 (Good) with 3 views, 0 installs and 3 GitHub stars.