← Explore all mcp servers

FEATURE MANAGEMENT / ConfigCat

ConfigCat MCP Server

Inspect and change feature flags, configurations, environments and organization settings through ConfigCat Management API.

“Inspect and change feature flags, configurations, environments and organization settings through ConfigCat Management API.”

01 / THE REASONING

Why this made the selection.

  • Inspect and change feature flags, configurations, environments and organization settings through ConfigCat Management API.
  • The setup documentation makes this operating boundary explicit: The credential can expose product/environment deletion, member permission changes and SDK-key retrieval as well as flag reads.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md
  • LICENSE
  • package.json
  • src/http.ts

Our findings

  • The credential can expose product/environment deletion, member permission changes and SDK-key retrieval as well as flag reads.
  • This is a management integration, not just SDK documentation. API rate limits still apply and exposed tools can affect production feature behavior.

Not established by this review

  • No server installation, authentication, live tool execution or isolation test was performed.
  • Package/container parity with the pinned source and transitive dependency security were not established.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

npx -y @configcat/mcp-server

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Run npx -y @configcat/mcp-server with Node.js >=20 and CONFIGCAT_API_USER/CONFIGCAT_API_PASS from Management API credentials. Set CONFIGCAT_BASE_URL only for the intended API host.
  2. Verify the connected account, available tools and target resource before authorizing mutations.

Before you start

  • Pinned package Node.js requirement: >=20.0.0.
  • A compatible local process MCP client.
  • The credential can expose product/environment deletion, member permission changes and SDK-key retrieval as well as flag reads.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/configcat/mcp-server/blob/70919cf24bc61440bcd85f911f57ef4b4d0caaee/README.md

    Supports: description, setup, capabilities, review, limitations

  2. https://github.com/configcat/mcp-server/blob/70919cf24bc61440bcd85f911f57ef4b4d0caaee/LICENSE

    Supports: license

  3. Pinned package metadata ↗Checked

    https://github.com/configcat/mcp-server/blob/70919cf24bc61440bcd85f911f57ef4b4d0caaee/package.json

    Supports: install, language, review

  4. https://github.com/configcat/mcp-server/blob/70919cf24bc61440bcd85f911f57ef4b4d0caaee/src/http.ts

    Supports: review, install, access, limitations

Evidence & Ask