All servers / Developer / ConfigCat MCP server
ConfigCat MCP server
MCP server exposing ConfigCat Public Management API (products, configs, environments, values v1/v2).
Tested by ConnectATDScore 88 out of 100. Tested 2026-11-18 on package version 0.2.1. Package: @configcat/mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 18 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.2 seconds including download)
- Tools offered: 96
- Last published: 2026-11-02
- Weekly downloads (npm): 1,661
- License: MIT · Direct dependencies: 7
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get-change-request1 of 1 parameter describedReturns the details of a specific Change Request.
update-change-request2 of 2 parameters describedUpdates the metadata of a Change Request, such as title, note, schedule, etc.
list-change-requests10 of 10 parameters describedReturns Change Requests of a Product with optional filtering and pagination.
list-organizationsno parametersThis endpoint returns the list of the Organizations that belongs to the user.
list-productsno parametersThis endpoint returns the list of the Products that belongs to the user.
list-tags1 of 1 parameter describedThis endpoint returns the list of the Tags in a specified Product, identified by the `productId` parameter.
create-tag1 of 2 parameters describedThis endpoint creates a new Tag in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
list-webhooks1 of 1 parameter describedThis endpoint returns the list of the Webhooks that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
list-configs1 of 1 parameter describedThis endpoint returns the list of the Configs that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
create-config1 of 2 parameters describedThis endpoint creates a new Config in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
list-environments1 of 1 parameter describedThis endpoint returns the list of the Environments that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
create-environment1 of 2 parameters describedThis endpoint creates a new Environment in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
list-permission-groups1 of 1 parameter describedThis endpoint returns the list of the Permission Groups that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
create-permission-group1 of 2 parameters describedThis endpoint creates a new Permission Group in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
list-integrations1 of 1 parameter describedThis endpoint returns the list of the Integrations that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
create-integration1 of 2 parameters describedThis endpoint creates a new Integration in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint. The Parameters dictionary differs for each IntegrationType: - Datadog - `apikey`: Required. Datadog API key. - `site`: Datadog site. Available values: `Us`, `Eu`, `Us1Fed`, `Us3`, `Us5`. Default: `Us`. - Slack Connecting the Slack integration through the Public Management API will not post messages with the ConfigCat Feature Flags Slack app but with an incoming webhook. - `incoming_webhook.url`: Required. The [incoming webhook URL](https://api.slack.com/messaging/webhooks) where the integration should post messages. - `includeSensitiveData`: Set to "true" to include [sensitive (hashed) comparison values](https://configcat.com/docs/targeting/targeting-rule/user-condition/#confidential-text-comparators). By default, the integration will mask these values in the posted messages. We recommend hiding sensitive comparison values for shared or public Slack channels. - Amplitude - `apiKey`: Required. Amplitude API Key. - `secretKey`: Required. Amplitude Secret Key. - Mixpanel - `serviceAccountUserName`: Required. Mixpanel Service Account Username. - `serviceAccountSecret`: Required. Mixpanel Service Account Secret. - `projectId`: Required. Mixpanel Project ID. - `server`: Mixpanel Server. Available values: `StandardServer`, `EUResidencyServer`. Default: `StandardServer`. - Twilio Segment - `writeKey`: Required. Twilio Segment Write Key. - `server`: Twilio Segment Server. Available values: `Us`, `Eu`. Default: `Us`. - PubNub (work in progress)
list-segments1 of 1 parameter describedThis endpoint returns the list of the Segments that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
create-segment1 of 2 parameters describedThis endpoint creates a new Segment in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
list-settings1 of 1 parameter describedThis endpoint returns the list of the Feature Flags and Settings defined in a specified Config, identified by the `configId` parameter.
create-setting1 of 2 parameters describedThis endpoint creates a new Feature Flag or Setting in a specified Config identified by the `configId` parameter. **Important:** The `key` attribute must be unique within the given Config.
list-auditlogs8 of 8 parameters describedThis endpoint returns the list of Audit log items for a given Product and the result can be optionally filtered by Config and/or Environment.
list-staleflags6 of 6 parameters describedThis endpoint returns the list of Zombie (stale) flags for a given Product and the result can be optionally filtered by various parameters.
get-code-references1 of 1 parameter describedGet References for Feature Flag or Setting
get-config1 of 1 parameter describedThis endpoint returns the metadata of a Config identified by the `configId`.
update-config1 of 2 parameters describedThis endpoint updates a Config identified by the `configId` parameter.
delete-config1 of 1 parameter describedThis endpoint removes a Config identified by the `configId` parameter.
get-environment1 of 1 parameter describedThis endpoint returns the metadata of an Environment identified by the `environmentId`.
update-environment2 of 2 parameters describedThis endpoint updates an Environment identified by the `environmentId` parameter.
delete-environment2 of 2 parameters describedThis endpoint removes an Environment identified by the `environmentId` parameter. If the `cleanupAuditLogs` flag is set to true, it also deletes the audit log records related to the environment (except for the `Created a new environment` and `Deleted an environment` records).
get-permission-group1 of 1 parameter describedThis endpoint returns the metadata of a Permission Group identified by the `permissionGroupId`.
update-permission-group1 of 2 parameters describedThis endpoint updates a Permission Group identified by the `permissionGroupId` parameter.
delete-permission-group1 of 1 parameter describedThis endpoint removes a Permission Group identified by the `permissionGroupId` parameter.
get-integration1 of 1 parameter describedThis endpoint returns the metadata of an Integration identified by the `integrationId`.
update-integration1 of 2 parameters describedThis endpoint updates a Config identified by the `integrationId` parameter. The Parameters dictionary differs for each IntegrationType: - Datadog - `apikey`: Required. Datadog API key. - `site`: Datadog site. Available values: `Us`, `Eu`, `Us1Fed`, `Us3`, `Us5`. Default: `Us`. - Slack Connecting the Slack integration through the Public Management API will not post messages with the ConfigCat Feature Flags Slack app but with an incoming webhook. - `incoming_webhook.url`: Required. The [incoming webhook URL](https://api.slack.com/messaging/webhooks) where the integration should post messages. - `includeSensitiveData`: Set to "true" to include [sensitive (hashed) comparison values](https://configcat.com/docs/targeting/targeting-rule/user-condition/#confidential-text-comparators). By default, the integration will mask these values in the posted messages. We recommend hiding sensitive comparison values for shared or public Slack channels. - Amplitude - `apiKey`: Required. Amplitude API Key. - `secretKey`: Required. Amplitude Secret Key. - Mixpanel - `serviceAccountUserName`: Required. Mixpanel Service Account Username. - `serviceAccountSecret`: Required. Mixpanel Service Account Secret. - `projectId`: Required. Mixpanel Project ID. - `server`: Mixpanel Server. Available values: `StandardServer`, `EUResidencyServer`. Default: `StandardServer`. - Twilio Segment - `writeKey`: Required. Twilio Segment Write Key. - `server`: Twilio Segment Server. Available values: `Us`, `Eu`. Default: `Us`. - PubNub (work in progress)
delete-integration1 of 1 parameter describedThis endpoint removes a Integration identified by the `integrationId` parameter.
get-sdk-keys2 of 2 parameters describedThis endpoint returns the SDK Key for your Config in a specified Environment.
list-organization-auditlogs9 of 9 parameters describedThis endpoint returns the list of Audit log items for a given Organization and the result can be optionally filtered by Product and/or Config and/or Environment.
list-organization-members1 of 1 parameter describedThis endpoint returns the list of Members that belongs to the given Organization, identified by the `organizationId` parameter. The results may vary based on the access level of the user who calls the endpoint: - When it's called with Organization Admin privileges, the result will contain each member in the Organization. - When it's called without Organization Admin privileges, the result will contain each Organization Admin along with members of those products where the caller has `Team members and permission groups` (`canManageMembers`) permission.
list-pending-invitations-org1 of 1 parameter describedThis endpoint returns the list of pending invitations within the given Organization identified by the `organizationId` parameter.
list-pending-invitations1 of 1 parameter describedThis endpoint returns the list of pending invitations within the given Product identified by the `productId` parameter.
list-predefined-variations1 of 1 parameter describedThis endpoint returns the predefined variations along with their usages in the Environments for a Feature Flag or Setting identified by the `settingId` parameter.
update-predefined-variations1 of 2 parameters describedThis endpoint updates the predefined variations for a Feature Flag or Setting identified by the `settingId` parameter. **Important:** You can only update a predefined variation's value if it is not used anywhere in your feature flags.
get-product1 of 1 parameter describedThis endpoint returns the metadata of a Product identified by the `productId`.
update-product1 of 2 parameters describedThis endpoint updates a Product identified by the `productId` parameter.
delete-product1 of 1 parameter describedThis endpoint removes a Product identified by the `productId` parameter.
list-product-members1 of 1 parameter describedThis endpoint returns the list of Members that belongs to the given Product, identified by the `productId` parameter.
get-product-preferences1 of 1 parameter describedThis endpoint returns the preferences of a Product identified by the `productId`.
update-product-preferences1 of 2 parameters describedThis endpoint updates the preferences of a Product identified by the `productId` parameter.
get-change-request-proposed-changes2 of 2 parameters describedReturns the proposed changes to the Settings included in a Change Request.
update-change-request-proposed-changes2 of 3 parameters describedUpdates the proposed changes to the Settings included in a Change Request.
get-segment1 of 1 parameter describedThis endpoint returns the metadata of a Segment identified by the `segmentId`.
update-segment1 of 2 parameters describedThis endpoint updates a Segment identified by the `segmentId` parameter.
delete-segment1 of 1 parameter describedThis endpoint removes a Segment identified by the `segmentId` parameter.
get-setting1 of 1 parameter describedThis endpoint returns the metadata attributes of a Feature Flag or Setting identified by the `settingId` parameter.
replace-setting1 of 2 parameters describedThis endpoint replaces the whole value of a Feature Flag or Setting identified by the `settingId` parameter. **Important:** As this endpoint is doing a complete replace, it's important to set every other attribute that you don't want to change in its original state. Not listing one means it will reset.
delete-setting1 of 1 parameter describedThis endpoint removes a Feature Flag or Setting from a specified Config, identified by the `configId` parameter.
update-setting1 of 2 parameters describedThis endpoint updates the metadata of a Feature Flag or Setting with a collection of [JSON Patch](https://jsonpatch.com) operations in a specified Config. Only the `name`, `hint` and `tags` attributes are modifiable by this endpoint. The `tags` attribute is a simple collection of the [tag IDs](#operation/list-tags) attached to the given setting. The advantage of using JSON Patch is that you can describe individual update operations on a resource without touching attributes that you don't want to change. For example: We have the following resource. ```json { "settingId": 5345, "key": "myGrandFeature", "name": "Tihs is a naem with soem typos.", "hint": "This flag controls my grandioso feature.", "settingType": "boolean", "tags": [ { "tagId": 0, "name": "sample tag", "color": "whale" } ] } ``` If we send an update request body as below (it changes the `name` and adds the already existing tag with the id `2`): ```json [ { "op": "replace", "path": "/name", "value": "This is the name without typos." }, { "op": "add", "path": "/tags/-", "value": 2 } ] ``` Only the `name` and `tags` are updated and all the other attributes remain unchanged. So we get a response like this: ```json { "settingId": 5345, "key": "myGrandFeature", "name": "This is the name without typos.", "hint": "This flag controls my grandioso feature.", "settingType": "boolean", "tags": [ { "tagId": 0, "name": "sample tag", "color": "whale" }, { "tagId": 2, "name": "another tag", "color": "koala" } ] } ```
list-settings-by-tag1 of 1 parameter describedThis endpoint returns the list of the Settings that has the specified Tag, identified by the `tagId` parameter.
get-setting-value2 of 2 parameters describedThis endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the `environmentId` parameter. The most important attributes in the response are the `value`, `rolloutRules` and `percentageRules`. The `value` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting or Percentage Rules, or when there are no additional rules to evaluate. The `rolloutRules` and `percentageRules` attributes are representing the current Targeting and Percentage Rules configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/targeting/targeting-overview).
replace-setting-value3 of 4 parameters describedThis endpoint replaces the whole value of a Feature Flag or Setting in a specified Environment. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. **Important:** As this endpoint is doing a complete replace, it's important to set every other attribute that you don't want to change in its original state. Not listing one means it will reset. For example: We have the following resource. ```json { "rolloutPercentageItems": [ { "percentage": 30, "value": true }, { "percentage": 70, "value": false } ], "rolloutRules": [], "value": false } ``` If we send a replace request body as below: ```json { "value": true } ``` Then besides that the default value is set to `true`, all the Percentage Rules are deleted. So we get a response like this: ```json { "rolloutPercentageItems": [], "rolloutRules": [], "value": true } ``` The `rolloutRules` property describes two types of rules: - **Targeting rules**: When you want to add or update a targeting rule, the `comparator`, `comparisonAttribute`, and `comparisonValue` members are required. - **Segment rules**: When you want to add add or update a segment rule, the `segmentId` which identifies the desired segment and the `segmentComparator` members are required.
update-setting-value3 of 4 parameters describedThis endpoint updates the value of a Feature Flag or Setting with a collection of [JSON Patch](https://jsonpatch.com) operations in a specified Environment. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. The advantage of using JSON Patch is that you can describe individual update operations on a resource without touching attributes that you don't want to change. It supports collection reordering, so it also can be used for reordering the targeting rules of a Feature Flag or Setting. For example: We have the following resource. ```json { "rolloutPercentageItems": [ { "percentage": 30, "value": true }, { "percentage": 70, "value": false } ], "rolloutRules": [], "value": false } ``` If we send an update request body as below: ```json [ { "op": "replace", "path": "/value", "value": true } ] ``` Only the default value is going to be set to `true` and all the Percentage Rules are remaining unchanged. So we get a response like this: ```json { "rolloutPercentageItems": [ { "percentage": 30, "value": true }, { "percentage": 70, "value": false } ], "rolloutRules": [], "value": true } ``` The `rolloutRules` property describes two types of rules: - **Targeting rules**: When you want to add or update a targeting rule, the `comparator`, `comparisonAttribute`, and `comparisonValue` members are required. - **Segment rules**: When you want to add add or update a segment rule, the `segmentId` which identifies the desired segment and the `segmentComparator` members are required.
get-setting-value-v22 of 2 parameters describedThis endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the `environmentId` parameter. The most important fields in the response are the `defaultValue`, `targetingRules`, and `percentageEvaluationAttribute`. The `defaultValue` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting Rules, or when there are no additional rules to evaluate. The `targetingRules` represents the current Targeting Rule configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/targeting/targeting-overview/). The `percentageEvaluationAttribute` represents the custom [User Object](https://configcat.com/docs/targeting/user-object/) attribute that must be used for [percentage evaluation](https://configcat.com/docs/targeting/percentage-options/) of the Feature Flag or Setting.
replace-setting-value-v25 of 6 parameters describedThis endpoint replaces the value and the Targeting Rules of a Feature Flag or Setting in a specified Environment identified by the <a target="_blank" rel="noopener noreferrer" href="https://app.configcat.com/sdkkey">SDK key</a> passed in the `X-CONFIGCAT-SDKKEY` header. Only the `defaultValue`, `targetingRules`, and `percentageEvaluationAttribute` fields are modifiable by this endpoint. **Important:** As this endpoint is doing a complete replace, it's important to set every other field that you don't want to change to its original state. Not listing one means it will reset. For example: We have the following resource of a Feature Flag. ```json { "defaultValue": { "boolValue": false }, "targetingRules": [ { "conditions": [ { "userCondition": { "comparisonAttribute": "Email", "comparator": "sensitiveTextEquals", "comparisonValue": { "stringValue": "test@example.com" } } } ], "percentageOptions": [], "value": { "boolValue": true } } ] } ``` If we send a replace request body as below: ```json { "defaultValue": { "boolValue": true } } ``` Then besides that the default served value is set to `true`, all the Targeting Rules are deleted. So we get a response like this: ```json { "defaultValue": { "boolValue": true }, "targetingRules": [] } ```
update-setting-value-v25 of 6 parameters describedThis endpoint updates the value of a Feature Flag or Setting with a collection of [JSON Patch](https://jsonpatch.com) operations in a specified Environment. Only the `defaultValue`, `targetingRules`, and `percentageEvaluationAttribute` fields are modifiable by this endpoint. The advantage of using JSON Patch is that you can describe individual update operations on a resource without touching attributes that you don't want to change. It supports collection reordering, so it also can be used for reordering the targeting rules of a Feature Flag or Setting. For example: We have the following resource of a Feature Flag. ```json { "defaultValue": { "boolValue": false }, "targetingRules": [ { "conditions": [ { "userCondition": { "comparisonAttribute": "Email", "comparator": "sensitiveTextEquals", "comparisonValue": { "stringValue": "test@example.com" } } } ], "percentageOptions": [], "value": { "boolValue": true } } ] } ``` If we send an update request body as below: ```json [ { "op": "replace", "path": "/targetingRules/0/value/boolValue", "value": true } ] ``` Only the first Targeting Rule's `value` is going to be set to `false` and all the other fields are remaining unchanged. So we get a response like this: ```json { "defaultValue": { "boolValue": false }, "targetingRules": [ { "conditions": [ { "userCondition": { "comparisonAttribute": "Email", "comparator": "sensitiveTextEquals", "comparisonValue": { "stringValue": "test@example.com" } } } ], "percentageOptions": [], "value": { "boolValue": false } } ] } ```
get-setting-values2 of 2 parameters describedThis endpoint returns the value of a specified Config's Feature Flags or Settings identified by the `configId` parameter in a specified Environment identified by the `environmentId` parameter. The most important attributes in the response are the `value`, `rolloutRules` and `percentageRules`. The `value` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting or Percentage Rules, or when there are no additional rules to evaluate. The `rolloutRules` and `percentageRules` attributes are representing the current Targeting and Percentage Rules configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/targeting/targeting-overview/).
post-setting-values3 of 4 parameters describedThis endpoint replaces the values of a specified Config's Feature Flags or Settings identified by the `configId` parameter in a specified Environment identified by the `environmentId` parameter. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. **Important:** As this endpoint is doing a complete replace, it's important to set every other attribute that you don't want to change in its original state. Not listing one means it will reset. For example: We have the following resource. ```json { "settingValues": [ { "rolloutPercentageItems": [ { "percentage": 30, "value": true }, { "percentage": 70, "value": false } ], "rolloutRules": [], "value": false, "settingId": 1 } ] } ``` If we send a replace request body as below: ```json { "settingValues": [ { "value": true, "settingId": 1 } ] } ``` Then besides that the default value is set to `true`, all the Percentage Rules are deleted. So we get a response like this: ```json { "settingValues": [ { "rolloutPercentageItems": [], "rolloutRules": [], "value": true, "setting": { "settingId": 1 } } ] } ``` The `rolloutRules` property describes two types of rules: - **Targeting rules**: When you want to add or update a targeting rule, the `comparator`, `comparisonAttribute`, and `comparisonValue` members are required. - **Segment rules**: When you want to add add or update a segment rule, the `segmentId` which identifies the desired segment and the `segmentComparator` members are required.
get-setting-values-v22 of 2 parameters describedThis endpoint returns all Feature Flag and Setting values of a Config identified by the `configId` parameter in a specified Environment identified by the `environmentId` parameter. The most important fields in the response are the `defaultValue`, `targetingRules`. The `defaultValue` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting Rules, or when there are no additional rules to evaluate. The `targetingRules` represents the current Targeting Rule configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/targeting/targeting-overview/). The `percentageEvaluationAttribute` represents the custom [User Object](https://configcat.com/docs/targeting/user-object/) attribute that must be used for [percentage evaluation](https://configcat.com/docs/targeting/percentage-options/) of the Feature Flag or Setting.
post-setting-values-v25 of 6 parameters describedThis endpoint batch updates the Feature Flags and Settings of a Config identified by the `configId` parameter in a specified Environment identified by the `environmentId` parameter. Only those Feature Flags and Settings are updated which are part of the request, all the others are left untouched. **Important:** As this endpoint is doing a complete replace on those Feature Flags and Settings, which are set in the request. It's important to set every other field that you don't want to change in its original state. Not listing a field means that it will reset. For example: We have the following resource of a Feature Flag. ```json { "settingFormulas": [ { "defaultValue": { "boolValue": false }, "targetingRules": [ { "conditions": [ { "userCondition": { "comparisonAttribute": "Email", "comparator": "sensitiveTextEquals", "comparisonValue": { "stringValue": "test@example.com" } } } ], "percentageOptions": [], "value": { "boolValue": true } } ], "settingId": 1 } ] } ``` If we send a batch replace request body as below: ```json { "updateFormulas": [ { "defaultValue": { "boolValue": false }, "settingId": 1 } ] } ``` Then besides that the default value is set to `true`, all Targeting Rules of the related Feature Flag are deleted. So we get a response like this: ```json { "settingFormulas": [ { "defaultValue": { "boolValue": false }, "targetingRules": [], "setting": { "settingId": 1 } } ] } ```
get-tag1 of 1 parameter describedThis endpoint returns the metadata of a Tag identified by the `tagId`.
update-tag0 of 2 parameters describedThis endpoint updates a Tag identified by the `tagId` parameter.
delete-tag1 of 1 parameter describedThis endpoint deletes a Tag identified by the `tagId` parameter. To remove a Tag from a Feature Flag or Setting use the [Update Flag](#operation/update-setting) endpoint.
get-organization-usage-and-quota2 of 2 parameters describedThis endpoint returns the current usage and quota information for an Organization. You can optionally filter the result by Product using the `productId` query parameter. The response includes monthly aggregate values, detailed request statistics, and quota limits used to monitor consumption and over-limit conditions.
get-webhook1 of 1 parameter describedThis endpoint returns the metadata of a Webhook identified by the `webhookId`.
replace-webhook1 of 2 parameters describedThis endpoint replaces the whole value of a Webhook identified by the `webhookId` parameter. **Important:** As this endpoint is doing a complete replace, it's important to set every other attribute that you don't want to change in its original state. Not listing one means it will reset.
delete-webhook1 of 1 parameter describedThis endpoint removes a Webhook identified by the `webhookId` parameter.
update-webhook1 of 2 parameters describedThis endpoint updates a Webhook identified by the `webhookId` parameter with a collection of [JSON Patch](https://jsonpatch.com) operations. The advantage of using JSON Patch is that you can describe individual update operations on a resource without touching attributes that you don't want to change. For example: We have the following resource. ```json { "webhookId": 6, "url": "https://example.com/hook", "httpMethod": "post", "content": "null", "webHookHeaders": [] } ``` If we send an update request body as below (it changes the `content` field and adds a new HTTP header): ```json [ { "op": "replace", "path": "/content", "value": "Some webhook content." }, { "op": "add", "path": "/webHookHeaders/-", "value": { "key": "X-Custom-Header", "value": "Custom header value" } } ] ``` Only the `content` and `webHookHeaders` are updated and all the other attributes remain unchanged. So we get a response like this: ```json { "webhookId": 6, "url": "https://example.com/hook", "httpMethod": "post", "content": "Some webhook content.", "webHookHeaders": [ { "key": "X-Custom-Header", "value": "Custom header value", "isSecure": false } ] } ```
get-webhook-signing-keys1 of 1 parameter describedThis endpoint returns the signing keys of a Webhook identified by the `webhookId`. Signing keys are used for ensuring the Webhook requests you receive are actually sent by ConfigCat. <a href="https://configcat.com/docs/advanced/notifications-webhooks/#verifying-webhook-requests" target="_blank" rel="noopener noreferrer">Here</a> you can read more about Webhook request verification.
add-change-request-comment1 of 2 parameters describedAdds a new comment to the Change Request.
apply-change-request1 of 1 parameter describedApplies the Change Request. The proposed changes will be applied and published immediately.
approve-change-request1 of 1 parameter describedAdds your approval to the Change Request.
claim-change-request-ownership1 of 1 parameter describedClaims ownership of the Change Request.
close-change-request1 of 1 parameter describedCloses the Change Request without applying it.
create-change-request2 of 3 parameters describedCreates a new Change Request for the specified Config and Environment.
create-product1 of 2 parameters describedThis endpoint creates a new Product in a specified Organization identified by the `organizationId` parameter, which can be obtained from the [List Organizations](#operation/list-organizations) endpoint.
create-webhook2 of 3 parameters describedThis endpoint creates a new Webhook in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/list-products) endpoint.
invite-member1 of 2 parameters describedThis endpoint invites a Member into the given Product identified by the `productId` parameter.
remove-change-request-approval1 of 1 parameter describedRemoves your existing approval from the Change Request.
resolve-change-request-setting-conflicts2 of 3 parameters describedUpdates the proposed changes to a Setting included in the Change Request to resolve conflicts caused by concurrently published changes.
update-member-permissions2 of 3 parameters describedThis endpoint updates the permissions of a Member identified by the `userId`. This endpoint can also be used to move a Member between Permission Groups within a Product. Only a single Permission Group can be set per Product.
delete-organization-member2 of 2 parameters describedThis endpoint removes a Member identified by the `userId` from the given Organization identified by the `organizationId` parameter.
update-change-request-comment1 of 2 parameters describedUpdates an existing Change Request comment.
delete-change-request-comment1 of 1 parameter describedDeletes a Change Request comment.
delete-invitation1 of 1 parameter describedThis endpoint removes an Invitation identified by the `invitationId` parameter.
delete-product-member2 of 2 parameters describedThis endpoint removes a Member identified by the `userId` from the given Product identified by the `productId` parameter.
delete-change-request-proposed-change2 of 2 parameters describedRemoves a setting from a Change Request.
get-sdk-documentation1 of 1 parameter describedIf the user asks for coding related to a feature flag (such as integrating the ConfigCat SDK, adding a feature flag, or removing a feature flag), always call the tool "get-sdk-documentation" first to download the latest ConfigCat SDK documentation. 1. Analyze the SDK URLs listed in the following SDK Reference list. 2. Then call the tool "get-sdk-documentation" with specific URL from the SDK Reference list to fetch relevant documentation page. ## SDK Reference - [Android (Java) SDK Reference](https://configcat.com/docs/sdk-reference/android.md): ConfigCat Android SDK Reference. This is a step-by-step guide on how to use feature flags in your Android Java application. - [ConfigCat package for Laravel](https://configcat.com/docs/sdk-reference/community/laravel.md): ConfigCat package for Laravel. Implement feature flags within your PHP Laravel application using ConfigCat. - [ConfigCat SDK for Vue.js](https://configcat.com/docs/sdk-reference/community/vue.md): Unofficial Vue SDK for ConfigCat feature flags. Based on ConfigCat's JavaScript SDK. - [C++ SDK Reference](https://configcat.com/docs/sdk-reference/cpp.md): ConfigCat C++ SDK Reference. This is a step-by-step guide on how to use feature flags in your C++ application. - [Dart (Flutter) SDK Reference](https://configcat.com/docs/sdk-reference/dart.md): ConfigCat Dart (Flutter) SDK Reference. This is a step-by-step guide on how to use feature flags in your Dart (Flutter) apps. - [.NET SDK Reference](https://configcat.com/docs/sdk-reference/dotnet.md): ConfigCat .NET SDK Reference. This is a step-by-step guide on how to use feature flags in your .NET application. - [Using the ConfigCat SDK in DI‑Based .NET Applications](https://configcat.com/docs/sdk-reference/dotnet/generic-host.md): Using the ConfigCat SDK in DI-based .NET applications. This is a step-by-step guide on how to use feature flags in your ASP.NET Core applications and other modern .NET applications built on .NET Generic Host or .NET's standard dependency injection. - [Elixir SDK Reference](https://configcat.com/docs/sdk-reference/elixir.md): ConfigCat Elixir SDK Reference. This is a step-by-step guide on how to use feature flags in your Elixir project. - [Go SDK Reference](https://configcat.com/docs/sdk-reference/go.md): ConfigCat Go SDK Reference. This is a step-by-step guide on how to use feature flags in your Go applications. - [Swift (iOS) SDK Reference](https://configcat.com/docs/sdk-reference/ios.md): ConfigCat Swift (iOS) SDK Reference. This is a step-by-step guide on how to use feature flags in your iOS mobile application. - [Java SDK reference](https://configcat.com/docs/sdk-reference/java.md): ConfigCat Java SDK Reference. This is a step-by-step guide on how to use feature flags in your Java application. - [Browser (JavaScript) SDK](https://configcat.com/docs/sdk-reference/js/browser.md): ConfigCat Browser (JavaScript) SDK Reference. This is a step-by-step guide on how to use feature flags in your frontend applications and Web Workers running in the browser. - [Bun SDK](https://configcat.com/docs/sdk-reference/js/bun.md): ConfigCat Bun SDK Reference. This is a step-by-step guide on how to use feature flags in your Bun applications. - [Chromium Extension SDK](https://configcat.com/docs/sdk-reference/js/chromium-extension.md): ConfigCat Chromium Extension SDK Reference. This is a step-by-step guide on how to use feature flags in your extensions for Chromium-based browsers (Chrome, Edge, etc.) - [Cloudflare Worker SDK](https://configcat.com/docs/sdk-reference/js/cloudflare-worker.md): ConfigCat Cloudflare Worker SDK Reference. This is a step-by-step guide on how to use feature flags in your Cloudflare Workers. - [Deno SDK](https://configcat.com/docs/sdk-reference/js/deno.md): ConfigCat Deno SDK Reference. This is a step-by-step guide on how to use feature flags in your Deno applications. - [Node.js SDK](https://configcat.com/docs/sdk-reference/js/node.md): ConfigCat Node.js SDK Referenc…
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.