Florentine AI MCP vs Dbx
A side-by-side look at the Florentine AI MCP and Dbx MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Florentine AI MCP for databases work as a local process; choose Dbx 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 Florentine AI MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
florentine_list_collections, florentine_ask.
Choose Dbx 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 | 51/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 27,558 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Florentine AI MCP | View Dbx |
Tools & capabilities
Florentine AI MCP tools 2
florentine_list_collections-> Lists all currently active collections/tables that can be queried. That includes descriptions, keys and type of values.florentine_ask-> Receives a question and returns a query, query result or answer (depending on the `returnTypes` setting).
Dbx 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.
Florentine AI MCP
{
"mcpServers": {
"mcp-293": {
"command": "npx",
"args": [
"-y",
"@florentine-ai/mcp"
]
}
}
}
Dbx
{
"mcpServers": {
"dbx": {
"command": "npx",
"args": [
"-y",
"@dbx-app/mcp-server"
]
}
}
}
Frequently asked questions
Florentine AI MCP is categorized under Databases and uses a local stdio subprocess. Dbx belongs to Databases and uses a local stdio subprocess. Pick Florentine AI MCP for databases work and Dbx 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.
Florentine AI MCP has no declared pricing — check the project's own site. Dbx is listed as free. 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 mcp-293 and dbx as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Florentine AI MCP has a quality signal of 51/100 (Good) with 1 views, 0 installs and 6 GitHub stars. Dbx has 53/100 (Good) with 6 views, 0 installs and 27,558 GitHub stars.