Skip to main content
Glama
flipt-io

Flipt MCP Server

Official
by flipt-io

list_flags

Retrieve feature flags from a specified namespace in Flipt MCP Server. Use this tool to manage and evaluate flag states for AI-assisted decision-making and system integrations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceKeyYes

Implementation Reference

  • src/index.ts:165-196 (registration)
    Registration of the 'list_flags' MCP tool, including inline Zod input schema and handler function that fetches flags via fliptClient and returns formatted text content with metadata URI.
    server.tool(
      'list_flags',
      {
        namespaceKey: z.string().min(1),
      },
      async args => {
        try {
          const flags = await fliptClient.listFlags(args.namespaceKey);
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(flags, null, 2),
              },
            ],
            _meta: {
              uri: `flipt://namespaces/${args.namespaceKey}/flags`,
            },
          };
        } catch (error: any) {
          console.error(`Error listing flags for namespace ${args.namespaceKey}:`, error);
          return {
            content: [
              {
                type: 'text',
                text: `Failed to list flags: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
  • The inline handler function for the 'list_flags' tool that executes the logic: calls fliptClient.listFlags, formats as JSON text content, includes URI metadata, handles errors.
    async args => {
  • Zod input schema for the 'list_flags' tool requiring a non-empty namespaceKey string.
      namespaceKey: z.string().min(1),
    },
  • Helper method in FliptClient that calls the generated FlagsServiceApi.listFlags to retrieve flags for a namespace, with error handling and response normalization.
    async listFlags(namespaceKey: string) {
      try {
        const response = await this.flagsApi.listFlags(namespaceKey);
        if (response && response.flags) {
          return response.flags;
        } else {
          console.error('Unexpected response structure:', response);
          return [];
        }
      } catch (error) {
        console.error(`Error getting flags for namespace ${namespaceKey}:`, error);
        return [];
      }
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