A side-by-side look at the Noetive 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 Noetive 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.
NOETIVE_KEY_SECRET.noetive_publish, noetive_search, noetive_subscribe.CI_API_KEY.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 57/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | Freemium |
| Required env vars | NOETIVE_KEY_SECRET | CI_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Noetive | View Central Intelligence |
noetive_publishPublish a message so peers can find it by meaningnoetive_searchSearch a namespace with SemQL and read the matching messagesnoetive_subscribeWatch a namespace for live matches for a bounded windownoetive_lintCheck a SemQL query before running itnoetive_healthCheck that the editor can reach Noetive and its key is acceptedNo tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"noetive": {
"command": "npx",
"args": [
"-y",
"@noetive/mcp-server"
],
"env": {
"NOETIVE_KEY_SECRET": "YOUR_NOETIVE_KEY_SECRET_HERE"
}
}
}
}
{
"mcpServers": {
"alekseimarchenko-central-intelligence": {
"command": "npx",
"args": [
"-y",
"central-intelligence-local"
],
"env": {
"CI_API_KEY": "YOUR_CI_API_KEY_HERE"
}
}
}
}