Coproduct MCP Connector

Last updated: 2026-09-30

Coproduct is a feature-flag platform. This connector lets Claude manage your flags, segments, targeting rules, and SDK keys on your behalf, so you can run the platform from a conversation instead of a dashboard. Claude can also read the Coproduct SDK documentation to help you add an SDK to your app.

Requirements

You need a Coproduct account with a project already set up. The connector acts as you: it can only see and change what your account already has access to.

Connecting

Add a custom connector in Claude with this server URL:

https://mcp.coproduct.app/mcp

Claude will redirect you to Coproduct to sign in and approve access. You choose which permissions to grant during that approval step. To revoke access, email support@coproduct.app.

Permissions

Scopes divide access into pieces, so you can grant only what you need:

• Flags: read flag state and targeting, or read plus create, edit, toggle, and publish
• Segments: read user segments, or read plus create, edit, and delete
• SDK keys: read SDK keys, or read plus create, rotate, and revoke. A rotation or revocation still takes effect only once a person confirms it in the Coproduct dashboard
• Audit log: read your project's change history

Granting a write scope always includes its matching read scope.

Reading the SDK documentation needs no scope. It reads only public documentation and none of your account data.

What you can do

Once connected, you can ask Claude to, for example:

• List your projects, environments, flags, and segments
• Create or edit a flag, and manage its targeting rules
• Turn a flag on or off, or kill it in an emergency so every user falls back to the safe value
• Create, edit, or delete user segments
• Create an SDK key. Its secret is shown once, to you, in the SDK keys widget, and is left out of the tool result Claude reads
• Rotate or revoke an SDK key. Claude does not change the key itself. It creates a short-lived, single-use confirmation link, and a person signed in to the Coproduct dashboard confirms the change there. A rotation shows the new secret once, in the dashboard
• Review recent changes in your audit log
• Publish a project's environment so staged changes go live
• Read the Flutter and iOS SDK documentation to help integrate an SDK into your app. This reads only public documentation, needs no permission scope, and reads none of your account data. An SDK that is not published yet is labeled as such, and Claude will not install it

Reverting a change

The audit log records every write with the state it replaced. To undo one: read the relevant entry, take its old_value, and call the matching write tool with that prior state. old_value uses an internal shape that differs from what a write tool accepts, so translate it first:

• Rollout coverage: old_value.coverage is in basis points (10000 = 100%). Divide by 100 to get the percentage a targeting-rule edit expects.
• Rollout target: old_value.rollout is the internal form. A single variation is {type: "variation", variation: "<key>"}, which becomes rollout: {variation: "<key>"}. A weighted split is {type: "weights", weights: [{variation_key, percentage}]}, which becomes rollout: {weights: [{variation_key, percent}]} (drop type, and the field is percent, not percentage).
• Targeting condition: old_value.condition is the internal condition tree, not the {all_of, any_of, excluded} shape a write tool accepts. Re-express it from the segment keys it references. A condition reported as complex may not be expressible this way, and so may not be revertible.
• Rule description: pass old_value.description back as-is, or null to clear it.
• Rule order: a reordering entry's old_value.order is a rule-id list, passed back as-is.
• Pause: a pause reverts with the revive tool, an unpause with the kill tool (which also takes a reason).
• Archive: both directions go through the same update tool, passing is_archived: false to unarchive or is_archived: true to archive again.

A compound entry that changed more than one axis at once may need multiple tool calls to fully revert, or may not be fully automatable.

Support

Questions or issues? Email support@coproduct.app.

← Back to Coproduct