Influxdb3 MCP Server vs Statey

A side-by-side look at the Influxdb3 MCP Server and Statey MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Influxdb3 MCP Server logoInfluxdb3 MCP ServerDatabases · Local subprocess (stdio)Official MCP server for InfluxDB 3 Core/Enterprise/Cloud Dedicated82ExcellentAuth: api key required
S
StateyDatabases · Remote HTTP/SSE
An agent-native database over MCP: shared, validated, structured records in every AI chat.39FairAuth: oauth 2.0

Verdict: choose Influxdb3 MCP Server for databases work as a local process; choose Statey for databases over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Influxdb3 MCP Server logoChoose 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.
Explore Influxdb3 MCP Server

S
Choose Statey when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore Statey

Feature & specification comparison

Rows where the two servers differ are marked.

SpecInfluxdb3 MCP Server logoInfluxdb3 MCP Server
S
Statey
CategoryDatabasesDatabases
Quality signal82/100 · Excellent39/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthAPI key requiredOAuth 2.0
PricingBYOK (pay the provider)Not declared
Required env varsINFLUX_MCP_TOOL_PROFILENone listed
Verified owner VerifiedCommunity listing
GitHub stars38—
Directory activity 50 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools27Not listed

Tools & capabilities

Influxdb3 MCP Server tools 27

  • load_database_contextLoad optional custom database context and documentation
  • get_helpGet help and troubleshooting guidance for InfluxDB operations
  • write_line_protocolWrite data using InfluxDB line protocol
  • create_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 metadata
  • query_influxqlRun bounded read-only InfluxQL with structured response metadata
  • get_measurementsList all measurements (tables) in a database
  • get_measurement_schemaGet schema (columns/types) for a measurement/table
  • list_tablesList tables, also called measurements, in a database
  • +15 more on the listing page

Statey 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.

Influxdb3 MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "influxdata-influxdb3-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "usage"
      ],
      "env": {
        "INFLUX_MCP_TOOL_PROFILE": "YOUR_INFLUX_MCP_TOOL_PROFILE_HERE"
      }
    }
  }
}

Statey

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "statey": {
      "command": "npx",
      "args": [
        "-y",
        "statey"
      ]
    }
  }
}

Frequently asked questions

Influxdb3 MCP Server is categorized under Databases and uses a local stdio subprocess. Statey belongs to Databases and uses a remote HTTP/SSE transport. Pick Influxdb3 MCP Server for databases work and Statey 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. Statey has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 statey 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 50 views, 0 installs and 38 GitHub stars. Statey has 39/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.