Skip to main content
Glama
flipt-io

Flipt MCP Server

Official
by flipt-io

create_segment

Define user segments in Flipt MCP Server by specifying namespace, key, name, and match type for targeted feature flag evaluations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNo
keyYes
matchTypeYes
nameYes
namespaceKeyYes

Implementation Reference

  • Primary MCP tool registration, schema validation, and handler execution logic for 'create_segment'. Calls FliptClient.createSegment and handles response/error formatting.
    server.tool(
      'create_segment',
      {
        namespaceKey: z.string().min(1),
        key: z.string().min(1),
        name: z.string().min(1),
        description: z.string().optional(),
        matchType: z.enum(['ALL_MATCH_TYPE', 'ANY_MATCH_TYPE']),
      },
      async args => {
        try {
          const segment = await fliptClient.createSegment(
            args.namespaceKey,
            args.key,
            args.name,
            args.description,
            args.matchType
          );
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(segment, null, 2),
              },
            ],
            _meta: {
              uri: `flipt://namespaces/${args.namespaceKey}/segments/${args.key}`,
            },
          };
        } catch (error: any) {
          console.error('Error creating segment:', error);
          return {
            content: [
              {
                type: 'text',
                text: `Failed to create segment: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Zod input schema defining parameters for the create_segment tool.
    {
      namespaceKey: z.string().min(1),
      key: z.string().min(1),
      name: z.string().min(1),
      description: z.string().optional(),
      matchType: z.enum(['ALL_MATCH_TYPE', 'ANY_MATCH_TYPE']),
    },
  • FliptClient helper method that converts parameters and calls the generated segmentsApi.createSegment to interact with Flipt API.
    async createSegment(
      namespaceKey: string,
      key: string,
      name: string,
      description?: string,
      matchType?: string
    ) {
      try {
        const segmentMatchType =
          matchType === 'ALL_MATCH_TYPE'
            ? CreateSegmentRequestMatchTypeEnum.AllMatchType
            : CreateSegmentRequestMatchTypeEnum.AnyMatchType;
    
        const response = await this.segmentsApi.createSegment(namespaceKey, {
          key,
          name,
          description,
          matchType: segmentMatchType,
        });
        return response;
      } catch (error) {
        console.error('Error creating segment:', error);
        throw error;
      }
    }
  • Generated TypeScript model and enum for CreateSegmentRequest used in the Flipt API client.
    export class CreateSegmentRequest {
        'key': string;
        'name': string;
        'description'?: string;
        'matchType': CreateSegmentRequestMatchTypeEnum;
        'namespaceKey'?: string;
    
        static readonly discriminator: string | undefined = undefined;
    
        static readonly mapping: {[index: string]: string} | undefined = undefined;
    
        static readonly attributeTypeMap: Array<{name: string, baseName: string, type: string, format: string}> = [
            {
                "name": "key",
                "baseName": "key",
                "type": "string",
                "format": ""
            },
            {
                "name": "name",
                "baseName": "name",
                "type": "string",
                "format": ""
            },
            {
                "name": "description",
                "baseName": "description",
                "type": "string",
                "format": ""
            },
            {
                "name": "matchType",
                "baseName": "matchType",
                "type": "CreateSegmentRequestMatchTypeEnum",
                "format": "enum"
            },
            {
                "name": "namespaceKey",
                "baseName": "namespaceKey",
                "type": "string",
                "format": ""
            }    ];
    
        static getAttributeTypeMap() {
            return CreateSegmentRequest.attributeTypeMap;
        }
    
        public constructor() {
        }
    }
    
    export enum CreateSegmentRequestMatchTypeEnum {
        AllMatchType = 'ALL_MATCH_TYPE',
        AnyMatchType = 'ANY_MATCH_TYPE'
    }
  • Alternative handler method in ToolHandlers class for create_segment (appears unused as index.ts registers directly).
    async handleCreateSegment({
      namespaceKey,
      key,
      name,
      description,
      matchType,
    }: {
      namespaceKey: string;
      key: string;
      name: string;
      description?: string;
      matchType: string;
    }) {
      try {
        const segment = await this.fliptClient.createSegment(
          namespaceKey,
          key,
          name,
          description,
          matchType
        );
        return {
          content: [
            {
              type: 'text',
              text: `Successfully created segment: ${JSON.stringify(segment, null, 2)}`,
            },
          ],
        };
      } catch (error) {
        console.error(`Error creating segment in namespace ${namespaceKey}:`, error);
        return {
          content: [
            {
              type: 'text',
              text: `Error creating segment in namespace ${namespaceKey}: ${error}`,
            },
          ],
          isError: true,
        };
      }
    }
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