Skip to main content
Glama
configcat

ConfigCat MCP Server

Official
by configcat
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

update-integration

Update an existing integration's name, parameters, connected environments, and configs. Supports providers like Datadog, Slack, Amplitude, Mixpanel, and Twilio Segment.

Instructions

This 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 where the integration should post messages.

    • includeSensitiveData: Set to "true" to include sensitive (hashed) comparison values. 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)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
integrationIdYesThe identifier of the Integration.
requestBodyYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must cover behavioral aspects. It discloses that Slack integration uses a webhook instead of the app, and notes PubNub as 'work in progress'. However, it doesn't mention idempotency, destructive effects, or authorization requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: a brief opening sentence, followed by a clear, organized list of integration types with their parameters. Every sentence is informative, and the layout is scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple integration types with varying parameters), the description is thorough. No output schema exists, but the description explains inputs comprehensively. Minor gaps include missing return value details and non-parameter behaviors.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds extensive value beyond the schema by detailing required and optional parameters for each integration type (Datadog, Slack, Amplitude, etc.), including defaults and special cases. Schema coverage is high, but the description enriches it significantly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool updates a Config identified by integrationId, distinguishing it from creation or retrieval tools. It details integration-specific parameters, making the action unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for updating an existing integration but lacks explicit when-to-use or when-not-to-use guidance. It does contrast with Slack integration specifics but doesn't list alternatives or preconditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/configcat/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server