Databases, measurements and SQL or InfluxQL reads of InfluxDB 3, 2.x and 1.x. Writes wait for approval.
The screenshots show GateRook 2.0.0: the InfluxDB form, the endpoint selector, and this connector’s actual tool preview. The form and preview have not been saved. Select a screenshot to open it at full size.
1. Create a connection and enter the settings
In GateRook, open Connections, select Add connection, search for InfluxDB, choose its card and select Continue to configure.
Find the InfluxDB server URL and identify its API generation: InfluxDB 3 Core or Enterprise, 2.x or Cloud, or 1.x. The choice controls authentication and query support.
Prepare a token restricted to the intended databases or buckets for InfluxDB 3/2.x, or a username and password for 1.x.
Enter a Name, for example influxdb-demo. Your AI app uses this name to choose the connection.
Enter Server URL and check Server after detection. For InfluxDB Cloud Serverless or Dedicated, use the 2.x/Cloud choice for the supported InfluxQL and write APIs; this connector does not provide their Arrow Flight SQL interface.
Select the matching Authentication method and enter API token, or Username and Password. Fill Organization for a 2.x setup when required.
Restrict Databases to the intended databases or buckets. Review Rows per query and Response size under Advanced; add a private CA certificate (PEM) only when needed.
Choose Development, Staging or Production to match the service. Review the connector’s limit and access settings before continuing.
2. Test the connection and add it to an endpoint
Select Continue to test. GateRook checks the settings from your computer. Review the result and resolve any connection, certificate or permission error before continuing.
Check the server generation when a query API is unavailable. If the test authenticates but cannot read a bucket or database, verify the token’s permissions and the database restrictions.
After the test passes, select Continue to add to an endpoint. Choose the endpoint your AI app uses, review its tool modes, then select Save connection. GateRook offers default as the starter endpoint.
3. Use the connection from your AI IDE
After saving InfluxDB on the endpoint and passing its connection test, ask your AI app to use influxdb-demo, or the name you chose. If its tools are missing, confirm the endpoint assignment and refresh the MCP connection or start a new chat.
The preview below shows this connector’s default tools before saving. The table explains what each tool can do; connection settings, credentials and endpoint policies can restrict access further.
Start with a small read request. Replace example resource names with existing resources your connection may access. Open Activity after the call to inspect its connection, tool, arguments, policy decision and result metadata.
Ask your AI, for example
- “List the databases or buckets available through influxdb-demo.”
- “List the measurements in the telemetry database on influxdb-demo.”
- “Using influxdb-demo, show the latest five temperature readings from telemetry with the query language this server supports.”
| Tool | What it does | Starts as |
|---|---|---|
influxdb_list_databases | Databases agents may use (buckets on InfluxDB 2.x). | Read only |
influxdb_list_measurements | Measurements of one database (tables on InfluxDB 3). Pages with nextCursor. | Read only |
influxdb_describe | Tags and fields with their types of one measurement. | Read only |
influxdb_query | One read: SQL on InfluxDB 3, or InfluxQL SELECT and SHOW. GateRook reads each statement first and runs only reads; the connection caps rows and size. Flux isn't supported. | Read only |
influxdb_write | Line protocol for one database. You approve the exact points; a point with the same measurement, tags and timestamp as an existing one replaces its fields. Never retried. | Approval |
You can change each tool’s mode on the endpoint. Every call your AI makes appears in Activity.