Skip to main content
Glama
idoru

InfluxDB MCP Server

by idoru

create-bucket

Create a new bucket in InfluxDB for storing time-series data, specifying the organization ID, bucket name, and optional retention period for data management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe bucket name
orgIDYesThe organization ID
retentionPeriodSecondsNoRetention period in seconds (optional)

Implementation Reference

  • The handler function that executes the create-bucket tool logic. It sends a POST request to the InfluxDB API to create a new bucket with the given name, orgID, and optional retention rules.
    export async function createBucket({ name, orgID, retentionPeriodSeconds }) {
      console.log(`=== CREATE-BUCKET TOOL CALLED ===`);
      console.log(`Creating bucket: ${name}, orgID: ${orgID}`);
    
      try {
        const bucketData = {
          name,
          orgID,
          retentionRules: retentionPeriodSeconds
            ? [
              { type: "expire", everySeconds: retentionPeriodSeconds },
            ]
            : undefined,
        };
    
        console.log(`Creating bucket with data: ${JSON.stringify(bucketData)}`);
    
        // Use fetch directly instead of our wrapper
        const response = await fetch(`${INFLUXDB_URL}/api/v2/buckets`, {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            "Authorization": `Token ${INFLUXDB_TOKEN}`,
          },
          body: JSON.stringify(bucketData),
        });
    
        console.log(`Create bucket response status: ${response.status}`);
    
        if (!response.ok) {
          const errorText = await response.text();
          throw new Error(
            `Failed to create bucket: ${response.status} ${errorText}`,
          );
        }
    
        const bucketResponse = await response.json();
    
        console.log(`=== CREATE-BUCKET TOOL COMPLETED SUCCESSFULLY ===`);
        return {
          content: [{
            type: "text",
            text:
              `Bucket created successfully:\nID: ${bucketResponse.id}\nName: ${bucketResponse.name}\nOrganization ID: ${bucketResponse.orgID}`,
          }],
        };
      } catch (error) {
        console.error(`=== CREATE-BUCKET TOOL ERROR: ${error.message} ===`);
        return {
          content: [{
            type: "text",
            text: `Error creating bucket: ${error.message}`,
          }],
          isError: true,
        };
      }
    }
  • src/index.js:120-142 (registration)
    Registers the 'create-bucket' tool with the MCP server, including input schema validation using Zod and linking to the createBucket handler function.
    server.tool(
      "create-bucket",
      "Provision a new bucket under an organization so that subsequent write-data calls have a destination.",
      {
        name: z
          .string()
          .describe(
            "Friendly bucket name. Follow InfluxDB naming rules (alphanumeric, dashes, underscores).",
          ),
        orgID: z
          .string()
          .describe(
            "Organization ID (UUID) that will own the bucket. Retrieve it from the organizations resource or create-org output.",
          ),
        retentionPeriodSeconds: z
          .number()
          .optional()
          .describe(
            "Optional retention duration expressed in seconds. Omit for infinite retention.",
          ),
      },
      createBucket,
    );
  • Zod schema defining the input parameters for the create-bucket tool: name (string), orgID (string), retentionPeriodSeconds (optional number).
      name: z
        .string()
        .describe(
          "Friendly bucket name. Follow InfluxDB naming rules (alphanumeric, dashes, underscores).",
        ),
      orgID: z
        .string()
        .describe(
          "Organization ID (UUID) that will own the bucket. Retrieve it from the organizations resource or create-org output.",
        ),
      retentionPeriodSeconds: z
        .number()
        .optional()
        .describe(
          "Optional retention duration expressed in seconds. Omit for infinite retention.",
        ),
    },
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/idoru/influxdb-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server