MCP Confluent vs OneDroid Engram
A side-by-side look at the MCP Confluent and OneDroid Engram MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
O
OneDroid EngramDatabasesVersioned agent memory in your own Postgres: portable context, permissioned, audit trail.37FairAuth: not declaredVerdict: choose MCP Confluent for databases work as a local process; choose OneDroid Engram for databases. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Confluent when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
OChoose OneDroid Engram when
- You need dedicated capabilities in the Databases domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O OneDroid Engram | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 53/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 167 | — |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Confluent | View OneDroid Engram |
Tools & capabilities
MCP Confluent tools
No tool names declared yet. Check the project README from the listing page.
OneDroid Engram 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.
MCP Confluent
{
"mcpServers": {
"confluentinc-mcp-confluent": {
"command": "npx",
"args": [
"-y",
"@confluentinc/mcp-confluent"
]
}
}
}
OneDroid Engram
No confirmed install command for OneDroid Engram yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Confluent is categorized under Databases and uses a local stdio subprocess. OneDroid Engram belongs to Databases and uses an install path we have not confirmed yet. Pick MCP Confluent for databases work and OneDroid Engram for databases.
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. OneDroid Engram has no confirmed install command yet — follow its own setup instructions.
MCP Confluent is listed as free. Auth: other. OneDroid Engram 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 confluentinc-mcp-confluent and onedroid-engram as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Confluent has a quality signal of 53/100 (Good) with 5 views, 0 installs and 167 GitHub stars. OneDroid Engram has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.