Skip to main content
Glama
configcat

ConfigCat MCP Server

Official
by configcat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-sdk-documentation

Fetches ConfigCat SDK documentation by URL to support integrating, adding, or removing feature flags in code.

Instructions

If 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: 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: ConfigCat package for Laravel. Implement feature flags within your PHP Laravel application using ConfigCat.

  • ConfigCat SDK for Vue.js: Unofficial Vue SDK for ConfigCat feature flags. Based on ConfigCat's JavaScript SDK.

  • C++ SDK Reference: 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: 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: 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: 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: ConfigCat Elixir SDK Reference. This is a step-by-step guide on how to use feature flags in your Elixir project.

  • Go SDK Reference: 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: 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: ConfigCat Java SDK Reference. This is a step-by-step guide on how to use feature flags in your Java application.

  • Browser (JavaScript) SDK: 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: ConfigCat Bun SDK Reference. This is a step-by-step guide on how to use feature flags in your Bun applications.

  • Chromium Extension SDK: 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: ConfigCat Cloudflare Worker SDK Reference. This is a step-by-step guide on how to use feature flags in your Cloudflare Workers.

  • Deno SDK: ConfigCat Deno SDK Reference. This is a step-by-step guide on how to use feature flags in your Deno applications.

  • Node.js SDK: ConfigCat Node.js SDK Reference. This is a step-by-step guide on how to use feature flags in your Node.js applications.

  • ConfigCat SDK for JavaScript: ConfigCat SDK for JavaScript Reference. This is a step-by-step guide on how to use feature flags in your JavaScript applications.

  • Kotlin Multiplatform SDK Reference: ConfigCat Kotlin Multiplatform SDK Reference. This is a step-by-step guide on how to use feature flags in your Kotlin Multiplatform apps.

  • OpenFeature Providers: Integrate feature flags using OpenFeature's vendor-agnostic API with ConfigCat OpenFeature providers. Supported for .NET, Java, Python, Go, JavaScript, React, Node.js, and more.

  • Using ConfigCat's OpenFeature Provider in Angular: This is a step-by-step guide on how to use ConfigCat with the OpenFeature Angular SDK.

  • OpenFeature Provider for .NET: ConfigCat OpenFeature Provider for .NET. This is a step-by-step guide on how to use ConfigCat with the OpenFeature .NET SDK.

  • OpenFeature Provider for Go: ConfigCat OpenFeature Provider for Go. This is a step-by-step guide on how to use ConfigCat with the OpenFeature Go SDK.

  • OpenFeature Provider for Java: ConfigCat OpenFeature Provider for Java. This is a step-by-step guide on how to use ConfigCat with the OpenFeature Java SDK.

  • OpenFeature Provider for JavaScript: ConfigCat OpenFeature Provider for JavaScript. This is a step-by-step guide on how to use ConfigCat with the OpenFeature JavaScript SDK.

  • OpenFeature Provider for Kotlin: ConfigCat OpenFeature Provider for Kotlin. This is a step-by-step guide on how to use ConfigCat with the OpenFeature Kotlin SDK.

  • Using ConfigCat's OpenFeature Provider in NestJS: This is a step-by-step guide on how to use ConfigCat with the OpenFeature NestJS SDK.

  • OpenFeature Provider for Node.js: ConfigCat OpenFeature Provider for Node.js. This is a step-by-step guide on how to use ConfigCat with the OpenFeature Node.js SDK.

  • OpenFeature Provider for PHP: ConfigCat OpenFeature Provider for PHP. This is a step-by-step guide on how to use ConfigCat with the OpenFeature PHP SDK.

  • OpenFeature Provider for Python: ConfigCat OpenFeature Provider for Python. This is a step-by-step guide on how to use ConfigCat with the OpenFeature Python SDK.

  • Using ConfigCat's OpenFeature Provider in React: This is a step-by-step guide on how to use ConfigCat with the OpenFeature React SDK.

  • OpenFeature Provider for Ruby: ConfigCat OpenFeature Provider for Ruby. This is a step-by-step guide on how to use ConfigCat with the OpenFeature Ruby SDK.

  • OpenFeature Provider for Rust: ConfigCat OpenFeature Provider for Rust. This is a step-by-step guide on how to use ConfigCat with the OpenFeature Rust SDK.

  • OpenFeature Provider for Swift: ConfigCat OpenFeature Provider for Swift. This is a step-by-step guide on how to use ConfigCat with the OpenFeature Swift SDK.

  • ConfigCat SDK Overview: List of all supported technologies like .NET, Java, JavaScript, Node.js, Deno, Bun, Cloudflare Worker, PHP, Python, Ruby, Go, Android, Swift, iOS, Elixir, Dart, Flutter, Angular, React, Vue.js, Chromium Extension, Kotlin Multiplatform, Laravel, Server-Side Rendered apps, etc.

  • PHP SDK Reference: ConfigCat PHP SDK Reference. This is a step-by-step guide on how to use feature flags in your PHP application.

  • Python SDK Reference: ConfigCat Python SDK Reference. This is a step-by-step guide on how to use feature flags in your Python application.

  • React SDK Reference: ConfigCat React SDK Reference. This is a step-by-step guide on how to use feature flags in your React applications.

  • Ruby SDK Reference: ConfigCat Ruby SDK Reference. This is a step-by-step guide on how to use feature flags in your Ruby application.

  • Rust SDK Reference: ConfigCat Rust SDK Reference. This is a step-by-step guide on how to use feature flags in your Rust applications.

  • Using the ConfigCat SDK in Unity: Using the ConfigCat SDK in Unity. This is a step-by-step guide on how to use feature flags in your Unity project.

  • Unreal Engine SDK Reference: ConfigCat Unreal Engine SDK Reference. This is a step-by-step guide on how to use feature flags in your Unreal Engine project.

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to fetch SDK documentation from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. It does disclose that it fetches live/latest content and expects a URL taken from the supplied reference list, which is useful. It says nothing, however, about what is returned (raw markdown page?), error behavior on an unlisted or unreachable URL, or any network/rate constraints.

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

Conciseness3/5

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

The usage instruction is correctly front-loaded in the first paragraph, which is good. But the bulk of the definition is a ~45-entry list where nearly every entry repeats the identical boilerplate 'This is a step-by-step guide on how to use feature flags in your X application', padding length without adding discriminating information.

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?

For a single-parameter fetch tool with no output schema and no annotations, the description supplies the crucial missing piece — the set of valid documents and how to choose among them. The remaining gap is the shape of the response, which is implied ('documentation page') but not stated.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the generic 'The URL to fetch SDK documentation from' by enumerating the exact permissible URLs and their technology coverage. That effectively adds an implicit enum the schema lacks.

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?

States a specific verb and resource: download/fetch the latest ConfigCat SDK documentation page. The scope is scoped by 'coding related to a feature flag', which cleanly separates it from every sibling tool (all of which manage configs, settings, products, members, etc.).

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

Usage Guidelines5/5

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

Gives an explicit trigger ('if the user asks for coding related to a feature flag, such as integrating/adding/removing a flag') and an explicit ordering rule ('always call this tool first'), then a two-step procedure for picking the URL. No inference required about when to call it.

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

Deploy Server

Other Tools