The Flagsmith MCP Server is Flagsmith's official, Speakeasy-generated Model Context Protocol server for its Core and SDK APIs, letting AI assistants read and manage feature flags, remote config values, and environment/identity segmentation directly from a conversation. Built by Flagsmith, it is officially maintained and best for Coding & Dev.
by Flagsmith
About
The Flagsmith MCP Server is Flagsmith's official, Speakeasy-generated Model Context Protocol server for its Core and SDK APIs, letting AI assistants read and manage feature flags, remote config values, and environment/identity segmentation directly from a conversation. It ships as an installable Desktop Extension (`mcp-server.mcpb`) for Claude Desktop — drag-and-drop install with no additional setup — and as an npm package (`flagsmith`) for CLI-based clients, started with `npx flagsmith start --token-auth <your-api-token>` and wired into Claude Code, Cursor, Gemini, and Windsurf via each client's standard MCP config or one-line `mcp add` command. Progressive discovery keeps the tool surface manageable across the full Flagsmith API rather than dumping every endpoint into context at once. Typical use: ask Claude to "list all feature flags enabled for the beta segment in production" or "toggle the new-checkout-flow flag off for the EU environment," with the assistant calling the live Flagsmith API instead of requiring a dashboard visit. NOTE: as of this writing the repo carries an explicit "not yet ready for production use" notice from its Speakeasy-generated setup flow — expect rough edges and check the repo before depending on it for anything mission-critical.
Trust verdict
How grades are computed →Grade A (98/100, reliable) from 1 measured signal, based on repository evidence. Only one signal stands behind it, so treat the grade as provisional.
What was measured
- Repository maintenance100/100 · weight 20
The repository has been pushed to or released within the last six months. — last push 2026-03-13.
- Source verification100/100 · weight 25
The repository URL was confirmed to resolve against the live GitHub API and is not archived.
- Provenance90/100 · weight 10
Published and maintained by the vendor of the service it connects to, rather than by a third party.
- Listing ↔ repository match100/100 · weight 5
The listing name lines up with the linked repository Flagsmith/flagsmith-mcp.
What could not be measured
These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.
- Live MCP handshakeunknown
No remote endpoint to handshake — this server installs and runs locally over stdio, so there is nothing to probe from the outside.
- Measured uptimeunknown
No probe history recorded for this server yet.
- Tool-schema stabilityunknown
Drift is a difference between two successive checks, and this server has none recorded.
Installation
npx flagsmith start --token-auth <your-api-token>flagsmith confirmed live on the npm registry — checked August 17, 2026.
Categories
Frequently Asked Questions
What is Flagsmith MCP Server?
Who built Flagsmith MCP Server?
Is Flagsmith MCP Server free?
How do I install Flagsmith MCP Server?
What does Flagsmith MCP Server integrate with?
Repo Health
Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.
- Last commit
- 6mo ago
- Install
- npm
- Package
- flagsmith
Quick Info
- Install Type
- npm
- Author
- Flagsmith
- Categories
- 2
- Integrations
- 5
Related Servers
Everything
Reference/test server with prompts, resources, and tools. Perfect for testing MCP implementations.
Git
Tools to read, search, and manipulate Git repositories. Full Git operations support.
Sequential Thinking MCP Server
a single structured-reasoning tool that lets a model plan, revise and branch its own chain of thought instead of answering in one shot. Published by Anthropic as part of the official modelcontextprotocol/servers monorepo (89,000+ stars, actively maintained), it exposes exactly one tool — sequential_thinking — and that tool is the whole product. Each call carries a `thought` string plus bookkeeping fields: `thoughtNumber`, `totalThoughts`, and `nextThoughtNeeded`, which the model flips to false when it is done. The interesting fields are the optional ones. `isRevision` and `revisesThought` let the model go back and correct an earlier step rather than plowing ahead on a bad assumption; `branchFromThought` and `branchId` let it fork into an alternative line of reasoning and carry both forward; `needsMoreThoughts` lets it extend past its own original estimate when a problem turns out to be deeper than it looked. In practice you never call the tool by hand. You connect the server to an MCP host and ask a question that deserves more than one pass — plan a PostgreSQL 14 to 16 migration and revise if downtime exceeds five minutes, work out why a deploy only fails in production, compare three architectures and branch when an assumption breaks. You can tell it is working when the host inspector shows repeated sequential_thinking calls with a rising `thoughtNumber` rather than a single response. Install with `npx -y @modelcontextprotocol/server-sequential-thinking` — note the hyphenated package name, which differs from both the `sequentialthinking` directory in the repo and the Docker image `mcp/sequentialthinking`, a mismatch that breaks a lot of copied configs. A Docker image is published alongside the npm package, and the README carries one-click VS Code install buttons for both transports. Set `DISABLE_THOUGHT_LOGGING=true` if you do not want every thought written to the server log.
21st.dev Magic
Create crafted UI components inspired by the best 21st.dev design engineers.
GitHub MCP Server
authenticated access to the whole GitHub platform — repositories, files, branches, issues, pull requests, Actions runs, security alerts, discussions and notifications — from Claude, Cursor, VS Code, Copilot CLI and any other MCP host. There is no npm package for this server, and that trips up most people who try to install it: `@github/mcp-server` is not published to the npm registry, so any `npx` line you find for it will fail. GitHub ships it three other ways. The easiest is the hosted remote server at https://api.githubcopilot.com/mcp/, which needs no install at all — point an HTTP-transport MCP client at that URL and log in with OAuth (VS Code 1.101+, Claude Desktop, Claude Code, Cursor and Windsurf all support this). The second is the official Docker image ghcr.io/github/github-mcp-server, which is what the copy-paste command on this page runs; on github.com it now performs a browser-based OAuth login on first use and keeps the token in memory only, which is why the published Docker configs map a fixed loopback callback port (-p 127.0.0.1:8085:8085 with GITHUB_OAUTH_CALLBACK_PORT=8085) so the container can receive the callback. Prefer a token? Set GITHUB_PERSONAL_ACCESS_TOKEN instead — it takes precedence over OAuth, and the minimum useful scopes are repo, read:org and read:packages. The third is the native Go binary from the repository's releases, which needs no fixed port for the OAuth flow. GitHub Enterprise Server has no hosted option: use the local server with --gh-host or GITHUB_HOST set to your instance (include the https:// scheme — it defaults to http://, which GHES rejects). Toolsets can be narrowed with GITHUB_TOOLSETS, and an insiders channel is available at /mcp/insiders or via the X-MCP-Insiders header.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →