Loading...
The Flipt MCP server enables AI assistants to manage and evaluate feature flags within the Flipt platform, using a Model Context Protocol interface.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
The Flipt MCP server enables AI assistants to manage and evaluate feature flags within the Flipt platform, using a Model Context Protocol interface.
This server allows AI assistants to manage feature flags, which can be risky if not handled carefully. The use of an API key provides a basic level of security, but the potential for misconfiguration and the lack of rate limiting require careful monitoring and access control.
Performance will be largely dependent on the performance of the Flipt API. Consider the number of API calls made by the AI assistant and optimize prompts accordingly.
Cost will be primarily driven by the number of API calls made to the Flipt API. Monitor API usage and optimize prompts to minimize costs.
npx -y @smithery/cli install @flipt-io/mcp-server-flipt --client claudelistNamespacesLists all namespaces within Flipt.
Read-only operation.
createNamespaceCreates a new namespace in Flipt.
Creates a new resource, but does not modify existing ones.
updateNamespaceUpdates an existing namespace in Flipt.
Modifies existing resources, potentially impacting application behavior.
deleteNamespaceDeletes a namespace from Flipt.
Deletes a resource, which can have significant consequences.
listFlagsLists all feature flags within a given namespace.
Read-only operation.
createFlagCreates a new feature flag within a given namespace.
Creates a new resource, but does not modify existing ones.
updateFlagUpdates an existing feature flag.
Modifies existing resources, potentially impacting application behavior.
deleteFlagDeletes a feature flag.
Deletes a resource, which can have significant consequences.
evaluateFlagEvaluates a flag for a given entity.
Read-only operation.
toggleFlagToggles a flag on or off.
Modifies the state of a feature flag, directly impacting application behavior.
API Key
hybrid
This server allows AI assistants to manage feature flags, which can be risky if not handled carefully. The use of an API key provides a basic level of security, but the potential for misconfiguration and the lack of rate limiting require careful monitoring and access control.
The server provides full read and write access to Flipt's feature flag configurations. Exercise caution when granting autonomy, as incorrect configurations can have significant consequences. Consider implementing safeguards at the AI assistant level.
Production Tip
Implement thorough testing and monitoring of feature flag changes made through the MCP server to prevent unintended consequences in production.
It's a server that allows AI assistants to interact with Flipt, a feature flag management platform, using the Model Context Protocol.
You can install it via Smithery, npm, or Docker, as described in the README.
The server is configured using environment variables, such as `FLIPT_API_URL` and `FLIPT_API_KEY`.
The server uses an API key for authentication with the Flipt API.
The main risks are exposure of the Flipt API key and the potential for unintended changes to feature flag configurations.
Yes, but it's important to implement thorough testing and monitoring to prevent unintended consequences.
No, rollback capabilities are not built into the server itself. You would need to rely on Flipt's rollback mechanisms or implement your own.