Eppo ACTION
Toggle Feature Flag
Enable or disable a feature flag in a specific environment in Eppo. Use this when the user wants to turn a flag on or off in Production, Test, or another environment. Use List Feature Flags or Get Feature Flag first to find the numeric
flagId and to discover valid environmentId values from the flag's environments array. See the documentation- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Eppo account once, then configure and run Toggle Feature Flag from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "eppo-toggle-feature-flag",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
eppo: { authProvisionId: "apn_xxxxxxx" },
flagId: 10,
environmentId: 10,
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "eppo-toggle-feature-flag",
"configured_props": {
"eppo": { "authProvisionId": "apn_xxxxxxx" },
"flagId": 10,
"environmentId": 10
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "eppo",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "eppo-toggle-feature-flag",
arguments: {
flagId: 10,
environmentId: 10,
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
flagId Flag ID | integer | The numeric ID of the feature flag. Use List Feature Flags to discover flag IDs. Required |
environmentId Environment ID | integer | The numeric ID of the environment to toggle the flag in (e.g. Production, Test). Use Get Feature Flag to find valid environment IDs from the flag's environments array. Required |
enabled Enabled | boolean | Set to true to enable the flag in this environment, false to disable it. Required |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- eppo-toggle-feature-flag
- Version
- 0.0.2
- App
- Eppo
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗