Skip to main content
Glama
flipt-io

Flipt MCP Server

Official
by flipt-io

create_namespace

Add a new namespace to organize and manage feature flags, segments, and evaluations within the Flipt MCP Server. Input key and name to define the namespace structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNo
keyYes
nameYes

Implementation Reference

  • Inline asynchronous handler function that executes the core logic of the 'create_namespace' tool: invokes fliptClient.createNamespace with provided arguments, formats the success response as MCP content with JSON serialization and metadata URI, or returns an error response.
    async args => {
      try {
        const namespace = await fliptClient.createNamespace(args.key, args.name, args.description);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(namespace, null, 2),
            },
          ],
          _meta: {
            uri: `flipt://namespaces/${args.key}`,
          },
        };
      } catch (error: any) {
        console.error('Error creating namespace:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Failed to create namespace: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod schema for input validation of the 'create_namespace' tool parameters: requires non-empty string keys and names, optional description.
    {
      key: z.string().min(1),
      name: z.string().min(1),
      description: z.string().optional(),
    },
  • src/index.ts:36-70 (registration)
    Registration of the 'create_namespace' MCP tool on the McpServer instance, including name, input schema, and inline handler function.
    server.tool(
      'create_namespace',
      {
        key: z.string().min(1),
        name: z.string().min(1),
        description: z.string().optional(),
      },
      async args => {
        try {
          const namespace = await fliptClient.createNamespace(args.key, args.name, args.description);
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(namespace, null, 2),
              },
            ],
            _meta: {
              uri: `flipt://namespaces/${args.key}`,
            },
          };
        } catch (error: any) {
          console.error('Error creating namespace:', error);
          return {
            content: [
              {
                type: 'text',
                text: `Failed to create namespace: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Helper method in FliptClient service class that wraps the generated NamespacesServiceApi.createNamespace call to perform the actual namespace creation via the Flipt API, handling errors.
    async createNamespace(key: string, name: string, description?: string) {
      try {
        const response = await this.namespacesApi.createNamespace({
          key,
          name,
          description,
        });
        return response;
      } catch (error) {
        console.error('Error creating namespace:', 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