Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Flagsmith (BYOK) icon

Flagsmith (BYOK)

Read your Flagsmith Cloud organisations, projects, environments, feature flags, segments, tags and audit log with BYOK

Unify Dynamics LLC

Tools7read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderFlagsmithunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Flagsmith organisations do I have?
Tools called
list_organisations
Which Flagsmith projects do I have?
Tools called
list_projects
Which environments does my Flagsmith project have?
Tools called
list_environments
Which feature flags are stale in my Flagsmith project?
Tools called
list_features
Which segments exist in my Flagsmith project?
Tools called
list_segments
Which tags are used in my Flagsmith project?
Tools called
list_tags

About

Flagsmith (BYOK) lets an AI assistant read your own Flagsmith data through the Flagsmith API with a key you supply (organisation API key (Flagsmith Cloud)). Read-only: 7 tools (list_organisations, list_projects, list_environments, list_features, list_segments, list_tags, list_audit_logs). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.flagsmith.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Flagsmith. Flagsmith and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Flagsmith API (api.flagsmith.com) with a BYOK key; documentation: https://api.flagsmith.com/api/v1/swagger.json. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

7 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data7 tools
  • List organisationsList the Flagsmith organisations the key can access with name, role, seats and creation date.
  • List projectsList the Flagsmith projects with settings such as hide_disabled_flags, stale-flag threshold in days and whether feature owners are enforced.
  • List environmentsList environments (for example Development, Production) of a project with name, description and change request approval settings.
  • List featuresList feature flags of a project with type, default state and value, description, tags, lifecycle stage (new, live, stale, permanent,…
  • List segmentsList user segments of a project with name, description, whether feature overrides use them and update time.
  • List tagsList the tags of a project with label, color and description.
  • List audit logsList audit log entries of a project, newest first, with the log text, who made the change (email) and the object type.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-flagsmith.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 7 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-flagsmith.connectorbay.com/mcp
RESTPOST https://byok-flagsmith.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-flagsmith.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your organisation API key (Flagsmith Cloud) in the X-Upstream-Key header (get one at docs.flagsmith.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Flagsmith connector: questions and answers

What is the Flagsmith connector?

Flagsmith (BYOK) lets an AI assistant read your own Flagsmith data through the Flagsmith API with a key you supply (organisation API key… It is a hosted MCP server with 7 tools such as List organisations, List projects, List environments, List features, List segments, List tags, published by Unify Dynamics LLC. It is independent and not affiliated with Flagsmith.

How do I connect Flagsmith to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-flagsmith.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-flagsmith.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-flagsmith.json.

Do I need a Flagsmith account or API key?

Yes: this is a bring-your-own-key connector. Create a organisation API key (Flagsmith Cloud) at https://docs.flagsmith.com/integrating-with-flagsmith/flagsmith-api-overview/management-api/authentication and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Flagsmith read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Flagsmith connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

LaunchDarkly Teams and Applications (BYOK)

Read your LaunchDarkly teams, custom roles, applications and application versions, and Relay Proxy configuration names, with your own API access token

Live · MCP + REST9 tools

LaunchDarkly Code References (BYOK)

Read which repositories and branches reference your LaunchDarkly flags, flag reference statistics and removed-flag history with your own API access token

Live · MCP + REST7 tools

LaunchDarkly Experiments (BYOK)

Read your LaunchDarkly experiments, iterations, holdouts, layers and metric groups with your own API access token

Live · MCP + REST8 tools

LaunchDarkly Engineering Insights (BYOK)

Read your LaunchDarkly engineering insights (beta): deployments, flag events, insight scores and groups, and deployment frequency, with your own API access token

Live · MCP + REST6 tools

LaunchDarkly Integrations (BYOK)

Read your LaunchDarkly webhooks, audit log subscriptions, data export destinations and flag import, feature store and big segment store integrations with your own API access token

Live · MCP + REST9 tools

LaunchDarkly Releases (BYOK)

Read your LaunchDarkly release pipelines, release progress, flag workflows and approval requests with your own API access token

Live · MCP + REST8 tools

Documentation

Back to top

Flagsmith (BYOK) — connector documentation

  • MCP endpoint: https://byok-flagsmith.connectorbay.com/mcp
  • REST API: POST https://byok-flagsmith.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-flagsmith.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Flagsmith organisation API key (Flagsmith Cloud), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-flagsmith.connectorbay.com/health · Tool schemas: https://byok-flagsmith.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-flagsmith · agent@connectorbay.com

What Flagsmith (BYOK) is for

Flagsmith (BYOK) lets an AI assistant read your own Flagsmith data through the Flagsmith API with a key you supply (organisation API key (Flagsmith Cloud)). Read-only: 7 tools (list_organisations, list_projects, list_environments, list_features, list_segments, list_tags, list_audit_logs). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.flagsmith.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Flagsmith. Flagsmith and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Flagsmith organisations do I have?"
  • "Which Flagsmith projects do I have?"
  • "Which environments does my Flagsmith project have?"
  • "Which feature flags are stale in my Flagsmith project?"
  • "Which segments exist in my Flagsmith project?"
  • "Which tags are used in my Flagsmith project?"

What it does

  • list_organisations: List the Flagsmith organisations the key can access with name, role, seats and creation date.
  • list_projects: List the Flagsmith projects with settings such as hide_disabled_flags, stale-flag threshold in days and whether feature owners are enforced.
  • list_environments: List environments (for example Development, Production) of a project with name, description and change request approval settings.
  • list_features: List feature flags of a project with type, default state and value, description, tags, lifecycle stage (new, live, stale, permanent, needs_monitoring, to_remove) and number of segment overrides.
  • list_segments: List user segments of a project with name, description, whether feature overrides use them and update time.
  • list_tags: List the tags of a project with label, color and description.
  • list_audit_logs: List audit log entries of a project, newest first, with the log text, who made the change (email) and the object type.

BYOK key

You bring your own Flagsmith organisation API key (Flagsmith Cloud) (https://docs.flagsmith.com/integrating-with-flagsmith/flagsmith-api-overview/management-api/authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.flagsmith.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Flagsmith API (api.flagsmith.com) with a BYOK key; documentation: https://api.flagsmith.com/api/v1/swagger.json. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Flagsmith. Flagsmith and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Flagsmith account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Flagsmith (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Flagsmith (BYOK) is. Flagsmith (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Flagsmith data: Read your Flagsmith Cloud organisations, projects, environments, feature flags, segments, tags and audit log with BYOK. You bring your own Flagsmith organisation API key (Flagsmith Cloud); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Flagsmith call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.flagsmith.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Flagsmith rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Flagsmith receives. The request we make on your behalf, including the key and the arguments, under Flagsmith's own terms and privacy policy. Flagsmith acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Flagsmith gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Flagsmith data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Flagsmith (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Flagsmith at any time to end all access.

Children. Flagsmith (BYOK) is a general-audience service operated by the adult using the assistant, under Flagsmith's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Flagsmith (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Flagsmith (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Flagsmith (BYOK) provides: Read your Flagsmith Cloud organisations, projects, environments, feature flags, segments, tags and audit log with BYOK. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Flagsmith credentials and only access data you are allowed to access. Flagsmith's terms apply to your use of Flagsmith; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Flagsmith. Flagsmith and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Flagsmith returns, lightly trimmed; it may be incomplete, delayed or changed by Flagsmith. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Flagsmith account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Flagsmith's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Flagsmith may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Flagsmith key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Flagsmith takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-flagsmith

Flagsmith (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Flagsmith (BYOK) never asks for them.

Get Flagsmith (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Flagsmith organisation API key (Flagsmith Cloud). Create one at https://docs.flagsmith.com/integrating-with-flagsmith/flagsmith-api-overview/management-api/authentication, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Flagsmith. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Flagsmith.