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

Split (Harness FME) (BYOK)

Read your Split feature flags, segments, environments and traffic types (Harness Feature Management and Experimentation) with BYOK

Unify Dynamics LLC

Documentation
Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderSplit (Harness FME)unofficial, not affiliated
Works withMCP · RESTany agent

Try asking

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

Which Split projects do I have?
Tools called
list_workspaces
Which environments does my Split project have?
Tools called
list_environments
Which traffic types does my Split project use?
Tools called
list_traffic_types
Which feature flags exist in Split?
Tools called
list_feature_flags
What is the state of my Split flags in Production?
Tools called
list_feature_flag_definitions
Which Split segments exist?
Tools called
list_segments

About

Split (Harness FME) (BYOK) lets an AI assistant read your own Split (Harness FME) data through the Split (Harness FME) API with a key you supply (Split Admin API key (a read-only role is enough)). Read-only: 8 tools (list_workspaces, list_environments, list_traffic_types, list_feature_flags, list_feature_flag_definitions, list_segments, list_segments_in_environment, list_rollout_statuses). 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.split.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Split (Harness FME). Split (Harness FME) and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Split (Harness FME) API (api.split.io) with a BYOK key; documentation: https://docs.split.io/reference/authentication. 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.
Privacy policyTerms

What it can do

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

OpenAPI
Read your data8 tools
  • List workspacesList projects (workspaces) with id, name, type and Harness organization and project identifiers.
  • List environmentsList the environments of a project (id and name).
  • List traffic typesList the traffic types of a project (id, name and display attribute id), for example user or account.
  • List feature flagsList feature flags of a project with name, description, traffic type, rollout status (for example 0% in Production) and creation time.
  • List feature flag definitionsList feature flag definitions in one environment: kill status, default treatment, traffic allocation and last update and last traffic times.
  • List segmentsList segments of a project with name, description, traffic type and creation time.
  • List segments in environmentList the segments activated in one environment with name, traffic type and creation time.
  • List rollout statusesList the rollout statuses a flag can have in a project (id, name and description), for example Ramping or Killed.

Information

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

Connect it to your agent

Three ways in, the same 8 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-splitio.connectorbay.com/mcp
RESTPOST https://byok-splitio.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-splitio.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 Split Admin API key (a read-only role is enough) in the X-Upstream-Key header (get one at docs.split.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

Split (Harness FME) connector: questions and answers

What is the Split (Harness FME) connector?

Split (Harness FME) (BYOK) lets an AI assistant read your own Split (Harness FME) data through the Split (Harness FME) API with a key you supply… It is a hosted MCP server with 8 tools such as List workspaces, List environments, List traffic types, List feature flags, List feature flag definitions, List segments, published by Unify Dynamics LLC. It is independent and not affiliated with Split (Harness FME).

How do I connect Split (Harness FME) to Claude, ChatGPT or Cursor?

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

Do I need a Split (Harness FME) account or API key?

Yes: this is a bring-your-own-key connector. Create a Split Admin API key (a read-only role is enough) at https://docs.split.io/reference/create-an-api-key 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 Split (Harness FME) read-only?

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

Is the Split (Harness FME) 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

GitLab Runners (BYOK)

Read GitLab.com CI runners available to you, their status, managers and processed jobs with your own personal access token

Live · MCP + REST6 tools

Glama (BYOK)

Browse the Glama directory of MCP servers and remote MCP connectors, their quality scores, tools and hosted instances, with your own Glama API key

Live · MCP + REST7 tools

GlitchTip (BYOK)

Read your GlitchTip Cloud error issues, events, releases, projects, uptime monitors and status pages with BYOK

Live · MCP + REST9 tools

Global Fishing Watch (BYOK)

Search vessel identities, fishing and port events and fishing-effort statistics from the Global Fishing Watch API with your own API token

Live · MCP + REST5 tools

Global Forest Watch (BYOK)

Browse Global Forest Watch datasets and run read-only SQL queries on forest, land cover and alert data with your own Data API key

Live · MCP + REST10 tools

GlobalGiving (BYOK)

Browse GlobalGiving charity projects, vetted nonprofits, themes and countries with your own GlobalGiving API key

Live · MCP + REST11 tools

Documentation

Back to top

Split (Harness FME) (BYOK) — connector documentation

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

What Split (Harness FME) (BYOK) is for

Split (Harness FME) (BYOK) lets an AI assistant read your own Split (Harness FME) data through the Split (Harness FME) API with a key you supply (Split Admin API key (a read-only role is enough)). Read-only: 8 tools (list_workspaces, list_environments, list_traffic_types, list_feature_flags, list_feature_flag_definitions, list_segments, list_segments_in_environment, list_rollout_statuses). 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.split.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Split (Harness FME). Split (Harness FME) 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 Split projects do I have?"
  • "Which environments does my Split project have?"
  • "Which traffic types does my Split project use?"
  • "Which feature flags exist in Split?"
  • "What is the state of my Split flags in Production?"
  • "Which Split segments exist?"

What it does

  • list_workspaces: List projects (workspaces) with id, name, type and Harness organization and project identifiers.
  • list_environments: List the environments of a project (id and name).
  • list_traffic_types: List the traffic types of a project (id, name and display attribute id), for example user or account.
  • list_feature_flags: List feature flags of a project with name, description, traffic type, rollout status (for example 0% in Production) and creation time.
  • list_feature_flag_definitions: List feature flag definitions in one environment: kill status, default treatment, traffic allocation and last update and last traffic times.
  • list_segments: List segments of a project with name, description, traffic type and creation time.
  • list_segments_in_environment: List the segments activated in one environment with name, traffic type and creation time.
  • list_rollout_statuses: List the rollout statuses a flag can have in a project (id, name and description), for example Ramping or Killed.

BYOK key

You bring your own Split (Harness FME) Split Admin API key (a read-only role is enough) (https://docs.split.io/reference/create-an-api-key). 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.split.io 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 Split (Harness FME) API (api.split.io) with a BYOK key; documentation: https://docs.split.io/reference/authentication. 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 Split (Harness FME). Split (Harness FME) 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 Split (Harness FME) account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Split (Harness FME) (BYOK) — Privacy Policy

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

What Split (Harness FME) (BYOK) is. Split (Harness FME) (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Split (Harness FME) data: Read your Split feature flags, segments, environments and traffic types (Harness Feature Management and Experimentation) with BYOK. You bring your own Split (Harness FME) Split Admin API key (a read-only role is enough); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Split (Harness FME) 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.split.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Split (Harness FME) 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 Split (Harness FME) receives. The request we make on your behalf, including the key and the arguments, under Split (Harness FME)'s own terms and privacy policy. Split (Harness FME) acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Split (Harness FME) 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 Split (Harness FME) 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. Split (Harness FME) (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 Split (Harness FME) at any time to end all access.

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

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

Terms of service

Back to top

Split (Harness FME) (BYOK) — Terms of Service

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

  1. The Service. Split (Harness FME) (BYOK) provides: Read your Split feature flags, segments, environments and traffic types (Harness Feature Management and Experimentation) 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 Split (Harness FME) credentials and only access data you are allowed to access. Split (Harness FME)'s terms apply to your use of Split (Harness FME); 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 Split (Harness FME). Split (Harness FME) 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 Split (Harness FME) returns, lightly trimmed; it may be incomplete, delayed or changed by Split (Harness FME). Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Split (Harness FME) 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 Split (Harness FME)'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; Split (Harness FME) 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 Split (Harness FME) 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 Split (Harness FME) 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-splitio

Support

Back to top

Split (Harness FME) (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. Split (Harness FME) (BYOK) never asks for them.

Get Split (Harness FME) (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Split (Harness FME) Split Admin API key (a read-only role is enough). Create one at https://docs.split.io/reference/create-an-api-key, 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 Split (Harness FME). Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Split (Harness FME).