Skip to main content
Glama
idoru

InfluxDB MCP Server

by idoru

create-org

Set up and manage InfluxDB organizations by specifying a name and optional description, enabling structured data organization and access within the MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoOrganization description (optional)
nameYesThe organization name

Implementation Reference

  • The main handler function for the 'create-org' tool. It makes a POST request to the InfluxDB API to create a new organization with the given name and optional description, then returns the org details or an error message.
    export async function createOrg({ name, description }) {
      try {
        const orgData = {
          name,
          description,
        };
    
        const response = await influxRequest("/api/v2/orgs", {
          method: "POST",
          body: JSON.stringify(orgData),
        });
    
        const org = await response.json();
    
        return {
          content: [{
            type: "text",
            text:
              `Organization created successfully:\nID: ${org.id}\nName: ${org.name}\nDescription: ${org.description || "N/A"
              }`,
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error creating organization: ${error.message}`,
          }],
          isError: true,
        };
      }
    }
  • src/index.js:143-160 (registration)
    Registers the 'create-org' tool on the MCP server, including its name, description, input schema using Zod, and references the createOrg handler function.
    server.tool(
      "create-org",
      "Create a brand-new organization to isolate users or projects before generating buckets and tokens.",
      {
        name: z
          .string()
          .describe(
            "Display name for the organization as it should appear in InfluxDB Cloud/OSS.",
          ),
        description: z
          .string()
          .optional()
          .describe(
            "Optional free-form description that helps humans understand why the org exists.",
          ),
      },
      createOrg,
    );
  • Zod schema defining the input parameters for the 'create-org' tool: required 'name' string and optional 'description' string.
      name: z
        .string()
        .describe(
          "Display name for the organization as it should appear in InfluxDB Cloud/OSS.",
        ),
      description: z
        .string()
        .optional()
        .describe(
          "Optional free-form description that helps humans understand why the org exists.",
        ),
    },
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