Compatible with every major AI agent and IDE
What is the Flagsmith MCP Server?
Connect your Flagsmith account to any AI agent to control feature releases and remote configurations through natural conversation.
What you can do
- Flag Management — Retrieve default flag states and remote configuration values for any environment instantly.
- Identity Control — Fetch specific flags and traits for user identities or identify new users with custom traits to test personalized experiences.
- Environment Admin — Create new environments within projects and fetch full configuration documents for local evaluation modes.
- Dynamic Updates — Update flag values (single or batch) and manage segment overrides using the Admin API for rapid iteration.
- Local Evaluation — Access the entire environment configuration document for high-performance SDK integrations.
How it works
- Subscribe to this server
- Enter your Flagsmith Environment Key or Admin API Key
- Start managing your feature lifecycle from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Developers — check flag states and user traits directly from the code editor to debug feature logic without switching contexts.
- Product Managers — toggle features, manage rollouts, and update remote configs without touching the dashboard.
- DevOps & SREs — automate environment creation and manage segment overrides through simple natural language commands.
Built-in capabilities (8)
Requires FLAGSMITH_API_KEY. Create a new environment within a project
Requires FLAGSMITH_API_KEY. Delete a segment override
Requires FLAGSMITH_ENVIRONMENT_KEY. Get the entire environment configuration document
Requires FLAGSMITH_ENVIRONMENT_KEY. Get all default flag states for an environment
Requires FLAGSMITH_ENVIRONMENT_KEY. Get flags and traits for a specific user identity
Requires FLAGSMITH_ENVIRONMENT_KEY. Identify user and set traits
Requires FLAGSMITH_API_KEY. Update a flag value (Single change)
Requires FLAGSMITH_API_KEY. Update flags (Batch change)
Why Cursor?
Cursor's Agent mode turns Flagsmith into an in-editor superpower. Ask Cursor to generate code using live data from Flagsmith and it fetches, processes, and writes. all in a single agentic loop. 8 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Flagsmith in Cursor
Flagsmith and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Flagsmith to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Flagsmith in Cursor
The Flagsmith MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Flagsmith for Cursor
Every tool call from Cursor to the Flagsmith MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I retrieve flags for a specific user identity?
Yes. Use the get_identity_flags tool by providing the user's identifier. The agent will return all flags and traits associated with that specific identity in the environment.
How do I update multiple feature flags at once?
You can use the update_flag_v2 tool for batch changes. Provide the environment key and a JSON payload containing the updates you wish to apply simultaneously.
Is it possible to create a new environment via the agent?
Yes, using the create_environment tool. You will need to provide a name for the environment and the target Project ID. This requires a valid Flagsmith Admin API Key.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
PharmWare
12 toolsAutomate cannabis laboratory testing via PharmWare — manage samples, track test results, issue Certificates of Analysis, and monitor lab workflows from any AI agent.

Azure Blob Container
4 toolsThis MCP does exactly one thing: it manages files in a single Azure Blob Container. That's its only function, and nothing else. Incredible for giving your AI secure file storage.

Tyk
12 toolsManage your Tyk API Gateway and Dashboard — create keys, manage security policies, and list API definitions via natural language.

Discord Webhook Notifier
1 toolsThis MCP does exactly one thing: it sends messages to your Discord channels. That's its only function, and nothing else. Zero friction, incredible for giving your AI agents a voice.
