Influxdb3 MCP Server vs Ravendb MCP
A side-by-side look at the Influxdb3 MCP Server and Ravendb MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Influxdb3 MCP Server for databases work as a local process; choose Ravendb MCP 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 Influxdb3 MCP Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
INFLUX_MCP_TOOL_PROFILE. - You want tools like
load_database_context, get_help, write_line_protocol.
Choose Ravendb MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
RAVENDB_URLS. - You want tools like
list_compare_exchange, get_database_stats, collect_debug_package.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 82/100 · Excellent | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | INFLUX_MCP_TOOL_PROFILE | RAVENDB_URLS |
| Verified owner | Verified | Community listing |
| GitHub stars | 38 | 2 |
| Directory activity | 45 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 27 | 21 |
| Full listing | View Influxdb3 MCP Server | View Ravendb MCP |
Tools & capabilities
Influxdb3 MCP Server tools 27
load_database_contextLoad optional custom database context and documentationget_helpGet help and troubleshooting guidance for InfluxDB operationswrite_line_protocolWrite data using InfluxDB line protocolcreate_databaseCreate a new database (with cloud-specific config options)update_databaseUpdate database configuration (retention for all; maxTables/maxColumns for Cloud Dedicated/Clustered)delete_databaseDelete a database by name (irreversible)execute_queryRun a SQL query against a database (supports multiple formats)query_sqlRun bounded read-only SQL with structured response metadataquery_influxqlRun bounded read-only InfluxQL with structured response metadataget_measurementsList all measurements (tables) in a databaseget_measurement_schemaGet schema (columns/types) for a measurement/tablelist_tablesList tables, also called measurements, in a database- +15 more on the listing page
Ravendb MCP tools 21
list_compare_exchangeList cluster-wide compare-exchange (cmpxchg) key/value entries — used for atomic guards, unique constraints, and cluster-transaction state. Optional startsWith key prefix; paged (1-1024, default 100). Not document-scoped.get_database_statsPer-database statistics and state. Sections: Summary, Detailed, Collections, Indexing, IndexErrors, Storage, Tombstones, Metrics, Identities, Revisions, Sharding, HugeDocuments, Io. Choose with include; default is Summary + Collections + Indexing. For one index's deep performance/debug use get_index; for one storage environment's deep report use inspect_storage. Tombstones/Metrics/Sharding are availability-wrapped (e.g. Sharding only on sharded databases).collect_debug_packageDownload a RavenDB debug/support package (zip) to a local artifact file. scope=Server (this node), Cluster (cluster-wide), or Database (one database — needs databaseName). Returns the artifact path, content type, and byte size. Heavy; for deep support investigations.get_indexOne index, multiple views. Sections: Definition (maps/reduce, fields, config, lock/deployment mode), Staleness (is it stale and why), Debug (internal debug view + metadata + history), Terms (distinct indexed terms for fieldName, paged), Errors (this index's indexing errors), Performance (this index's performance stats). Choose with include; default is Definition + Staleness. Terms requires fieldName. For an all-indexes view use get_database_stats with the indexing section.run_queryRead-only RQL (no UPDATE/patch; page start/pageSize 1-128). Features | where: and or not in all-in between startsWith endsWith exists regex search boost fuzzy proximity exact lucene intersect cmpxchg id | order: cast score random custom | select: distinct projection js declare load | group: count sum key array | include: counters timeseries revisions highlight | spatial facet suggest morelikethis vector.search. Names only; for syntax read rql://index then the feature resource — don't write RQL from memory.sample_live_feedPull a live server feed for a few seconds and return what streamed in. feed selects the source: AdminLogs (operational logs), ClusterDashboard (throughput/requests/indexing/storage), TrafficWatch (HTTP/TCP requests as they happen — optional databaseName filter), GcEvents, Allocations, ThreadContention, or ThreadRunaway (a one-shot snapshot, ignores seconds). seconds is the capture window, 1-30. ThreadRunaway returns the top-5 threads by CPU in full plus a compact index of all threads; pass threadNamePrefix for full detail on specific threads. Returns the captured text with Truncated/Limit flags when capped.get_database_configConfiguration of one database. Sections: Settings (effective config keys), ClientConfig (client config pushed to clients), Studio, and feature toggles/policies Expiration, Refresh, DataArchival, Revisions, DocumentsCompression, TimeSeries, SchemaValidation. Choose with include; default is all. Feature sections are projected from the database record; null means not configured.get_network_detailsTCP/network details: Stats (server connection counts + bytes), Connections (active TCP connections — server-wide, or per database when databaseName is given), DatabaseInfo (endpoint a client/node uses to reach a database on a node — needs databaseName + nodeTag). Choose sections with include; default is Stats + Connections.get_database_recordDatabase record: topology, ongoing tasks (backup/replication/ETL/subscriptions), settings, and feature configuration. Index definitions and history are reduced to name+count (they dominate the raw record) — use get_index for one index's full definition/staleness/history.list_databasesList all database names in the cluster. Call first to discover targets.get_ai_agentsRavenDB AI Agents configured on a database — conversational agents (their model connection, system prompt, tools, parameters). This is the AI Agents feature, NOT GenAI embeddings/connection-string tasks. Omit name to list all agents; pass name for one agent's configuration. Availability-wrapped: reports unavailable when AI Agents isn't enabled or licensed.get_live_workloadLive runtime activity: running (and longest-running) operations, currently running queries plus the query cache, and transaction info. Choose sections with include (default: all). Pass operationId to fetch one operation's state instead of the overview. databaseName is required for Queries and (with operationId) Operations; for Operations/Transactions without it, results are server-wide.- +9 more on 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.
Influxdb3 MCP Server
{
"mcpServers": {
"influxdata-influxdb3-mcp-server": {
"command": "npx",
"args": [
"-y",
"usage"
],
"env": {
"INFLUX_MCP_TOOL_PROFILE": "YOUR_INFLUX_MCP_TOOL_PROFILE_HERE"
}
}
}
}
Ravendb MCP
{
"mcpServers": {
"ravendb-mcp": {
"command": "npx",
"args": [
"-y",
"@ravendb/mcp"
],
"env": {
"RAVENDB_URLS": "YOUR_RAVENDB_URLS_HERE"
}
}
}
}
Frequently asked questions
Influxdb3 MCP Server is categorized under Databases and uses a local stdio subprocess. Ravendb MCP belongs to Databases and uses a local stdio subprocess. Pick Influxdb3 MCP Server for databases work and Ravendb MCP 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.
Influxdb3 MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Ravendb MCP 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 influxdata-influxdb3-mcp-server and ravendb-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Influxdb3 MCP Server has a quality signal of 82/100 (Excellent) with 45 views, 0 installs and 38 GitHub stars. Ravendb MCP has 60/100 (Good) with 1 views, 0 installs and 2 GitHub stars.