Prompts and Resources

Beyond individual tools, the Hyphen MCP server ships packaged prompts — multi-step workflows your assistant follows end to end — and resources it can read for context.

Table of Contents

• Prompts
  • deploy_app
  • rollout_feature_flag
  • cleanup_stale_flags
  • investigate_incident
  • analyze_link_performance
  • migrate_to_toggle
  • migrate_to_env
• Migration Guides
• Resources

Prompts

MCP prompts show up natively in your client: in Claude Code they appear as slash commands (/mcp__hyphen__deploy_app), in Claude Desktop and Cursor they're in the prompt picker. Each one turns a multi-step operation into a guided conversation, with your confirmation gating anything that changes state.

All arguments are optional unless noted — when omitted, the workflow discovers what it needs or asks you.

deploy_app

Turns a coding agent into a ship-it workflow for the repo it has open: detect the language, framework, and port; create the Hyphen project and app if needed; write the .hx link file; generate Docker packaging from the built-in examples; check ENV metadata; then deploy preview-first — hx deploy in your terminal when the working copy has uncommitted changes (only the CLI can package local code), a deployment run otherwise. It watches the run and logs, fixes failures, and promotes to production only after your explicit confirmation.

Arguments: project_id, app_id, environment.

rollout_feature_flag

Create or update a toggle, adjust its targeting (default value, percentage, or segments), and verify the rollout with a live edge evaluation — the flag should return the expected value for a representative target. Ends with a before/after summary and how to roll back.

Arguments: toggle_key (required), project_id, environment.

cleanup_stale_flags

Flag hygiene, done safely. Telemetry names the candidates (lifecycle intelligence tools find flags that are dormant or stuck on one value), a production evaluation confirms which branch the code should collapse to, your coding agent removes the flag conditionals from the codebase it already has open — and only after that change ships does delete_toggle retire the flag.

Arguments: project_id, toggle_key.

investigate_incident

Answers "what changed right before things broke?" — searches the audit log around the incident window, correlates with deployment runs, logs, and metrics, checks suspect flags with live evaluations, and presents a timeline with the most likely cause and the rollback or fix for each suspect.

Arguments: started_at, project_id, environment.

analyze_link_performance

Pulls click analytics for your short links — totals, referrers, countries, browsers, devices, clicks over time — summarizes trends and anomalies, and recommends next actions.

Arguments: code_id.

migrate_to_toggle

Guided migration to Hyphen Toggle: inventory the flags in your current system, recreate them as Hyphen toggles with equivalent targeting, swap your code to an OpenFeature provider, and verify with live edge evaluations before retiring the old system.

Arguments: source (e.g. launchdarkly, split, unleash), project_id, language.

migrate_to_env

Guided migration to Hyphen ENV: export secrets from the current store into per-environment .env files, push them with the CLI's end-to-end encryption (hx push), verify through metadata, and wire up the runtime. Secret values never pass through the server or the chat.

Arguments: source (e.g. dotenv, doppler, vault), app_id.

Migration Guides

The get_migration_guide tool backs the migration prompts and also works standalone — ask your assistant "help me migrate from LaunchDarkly to Hyphen" and it maps the old system's concepts onto Hyphen's, orders the steps, and names the MCP tool or hx CLI command for each one.

Resources

Resources are read-only context your assistant can attach to a conversation: