MCP Server Neon vs Titen Memory
A side-by-side look at the MCP Server Neon and Titen Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Neon for databases work as a local process; choose Titen Memory for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server Neon when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
NEON_API_KEY. - You want tools like
projects, branches, endpoints.
Choose Titen Memory when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 67/100 · Great | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | NEON_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 656 | 16 |
| Directory activity | 5 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 80 | Not listed |
| Full listing | View MCP Server Neon | View Titen Memory |
Tools & capabilities
MCP Server Neon tools 80
projectsbranchesendpointssnapshotsschemaqueryingneon_authdata_apiobservabilitydocsfunctionsstorage- +68 more on the listing page
Titen Memory 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 Server Neon
{
"mcpServers": {
"neondatabase-mcp-server-neon": {
"command": "npx",
"args": [
"-y",
"neon@latest"
],
"env": {
"NEON_API_KEY": "YOUR_NEON_API_KEY_HERE"
}
}
}
}
Titen Memory
{
"mcpServers": {
"titen-memory": {
"command": "npx",
"args": [
"-y",
"titen-memory"
]
}
}
}
Frequently asked questions
MCP Server Neon is categorized under Databases and uses a local stdio subprocess. Titen Memory belongs to Databases and uses a local stdio subprocess. Pick MCP Server Neon for databases work and Titen Memory 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.
MCP Server Neon is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. Titen Memory 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 neondatabase-mcp-server-neon and titen-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Neon has a quality signal of 67/100 (Great) with 5 views, 0 installs and 656 GitHub stars. Titen Memory has 47/100 (Fair) with 3 views, 0 installs and 16 GitHub stars.