Flagsmith

Created By
Flagsmitha day ago
Create, manage, and clean up Flagsmith feature flags directly from your AI tool. Flagsmith is an open source feature flag and remote config platform you can self-host or run in the cloud, and the MCP server lets you control flags, environments, and segments through natural language in any MCP-compatible editor.
Overview

Overview

What is the Flagsmith MCP Server?

The Flagsmith MCP (Model Context Protocol) Server connects your Flagsmith projects to AI assistants like Cursor, VS Code, and Claude.

It lets you create, read, update, and toggle feature flags, manage environments, and adjust segment targeting using natural language, without leaving your editor.

Flagsmith is open source, so you can point the server at Flagsmith Cloud or your own self-hosted instance.

How to use the Flagsmith MCP Server?

Add the server to any MCP-compatible client (Cursor, VS Code, Claude Desktop, Windsurf, or any IDE with MCP support), then provide your Flagsmith API key and, if you self-host, your API URL. Alternatively, you can also authenticate using OAuth. Once connected, you can manage flags by chatting with your AI tool.

Self-hosted users set FLAGSMITH_API_URL to their own instance. Flagsmith Cloud users can leave the default.

Key features of the Flagsmith MCP Server?

  • Create, read, update, and toggle feature flags across environments
  • Manage segments and targeting rules through natural language
  • Inspect flag states and configuration without opening the dashboard
  • Find and remove stale flags from your project
  • Works with Flagsmith Cloud or any self-hosted Flagsmith instance
  • Open source, with no vendor lock-in

Use cases of the Flagsmith MCP Server?

  • Flagging a new feature behind a flag while you write the code, in one conversation
  • Toggling a flag on or off in a specific environment during testing or rollout
  • Auditing and cleaning up stale flags across a project
  • Adjusting segment targeting rules without context-switching to the dashboard

FAQ from the Flagsmith MCP Server?

- What is a feature flag?

A feature flag is a technique that lets you turn features on or off without deploying new code, so you can release, test, and roll back safely.

- Do I need a Flagsmith account?

Yes. You need a Flagsmith API key from either Flagsmith Cloud or your own self-hosted instance.

- Can I use this with a self-hosted Flagsmith?

Yes. Set the API URL to your own instance and the server works exactly as it does against Flagsmith Cloud.

- Is Flagsmith open source?

Yes. Flagsmith is open source, so you can self-host it and avoid vendor lock-in.

- Which AI tools are supported?

Any client that supports the Model Context Protocol, including Cursor, VS Code, Claude Desktop, and Windsurf.

Server Config

{
  "mcpServers": {
    "flagsmith": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://127.0.0.1:8000/mcp"
      ]
    }
  }
}
Project Info
Created At
a day ago
Updated At
a day ago
Author Name
Flagsmith
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Meok Bs7121 Mcp

an hour ago
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

15 hours ago
Voyei

2 days ago