Skip to main content
Glama
flipt-io

Flipt MCP Server

Official
by flipt-io

create_variant

Generate variants for feature flags in Flipt MCP Server by specifying namespace, flag, and key details, enabling dynamic feature management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attachmentNo
descriptionNo
flagKeyYes
keyYes
nameNo
namespaceKeyYes

Implementation Reference

  • The main handler function for the MCP 'create_variant' tool. It processes the input arguments, calls the Flipt client to create the variant, and returns a formatted response or error message.
        try {
          const response = await fliptClient.createVariant(
            args.namespaceKey,
            args.flagKey,
            args.key,
            args.name,
            args.description,
            args.attachment
          );
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(response, null, 2),
              },
            ],
          };
        } catch (error: any) {
          console.error('Error creating variant:', error);
          return {
            content: [
              {
                type: 'text',
                text: `Failed to create variant: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Zod schema for input validation of the 'create_variant' tool parameters: namespaceKey, flagKey, key, name, description, attachment.
    {
      namespaceKey: z.string().min(1),
      flagKey: z.string().min(1),
      key: z.string().min(1),
      name: z.string().optional(),
      description: z.string().optional(),
      attachment: z.string().optional(),
    },
    async args => {
  • src/index.ts:844-886 (registration)
    Registration of the 'create_variant' MCP tool using server.tool with name, input schema, and handler function.
    server.tool(
      'create_variant',
      {
        namespaceKey: z.string().min(1),
        flagKey: z.string().min(1),
        key: z.string().min(1),
        name: z.string().optional(),
        description: z.string().optional(),
        attachment: z.string().optional(),
      },
      async args => {
        try {
          const response = await fliptClient.createVariant(
            args.namespaceKey,
            args.flagKey,
            args.key,
            args.name,
            args.description,
            args.attachment
          );
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(response, null, 2),
              },
            ],
          };
        } catch (error: any) {
          console.error('Error creating variant:', error);
          return {
            content: [
              {
                type: 'text',
                text: `Failed to create variant: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Helper method in FliptClient class that wraps the generated API call to create a variant, handling defaults and errors.
    async createVariant(
      namespaceKey: string,
      flagKey: string,
      key: string,
      name?: string,
      description?: string,
      attachment?: string
    ) {
      try {
        const response = await this.variantsApi.createVariant(namespaceKey, flagKey, {
          key,
          name: name || key,
          description,
          attachment,
        });
        return response;
      } catch (error) {
        console.error('Error creating variant:', error);
        throw error;
      }
    }
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/flipt-io/mcp-server-flipt'

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