http_mcp_headers

Extract GitHub Actions secrets from HTTP MCP headers and replace them with environment variable references.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/kaushal-waygood/agentic-self-healing-ci --skill http-mcp-headers-kaushal-waygood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: http_mcp_headers
Source: https://github.com/kaushal-waygood/agentic-self-healing-ci/tree/main/skills/http-mcp-headers
Command: npx skills add https://github.com/kaushal-waygood/agentic-self-healing-ci --skill http-mcp-headers-kaushal-waygood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that GitHub Actions secret expressions embedded in HTTP MCP tool headers are not leaked into generated MCP configs by extracting those expressions and converting them into safe environment variable references for execution steps.

Core Features & Use Cases

  • Secret Extraction: Detects ${{ secrets.* }} patterns in HTTP MCP headers and parses default fallbacks.
  • Config Rendering: Renders mcp-config.json headers using ${VAR} placeholders while adding an env passthrough section with escaped values.
  • Execution Mapping: Collects and emits execution-step environment variables that map to the original GitHub Actions secret expressions so workflows can inject secrets securely.
  • Use Case: Safely configure Datadog or other HTTP MCP servers to use repository secrets without embedding secret values in shared config files.

Quick Start

Generate an mcp-config.json for a workflow that uses HTTP MCP headers with GitHub Actions secrets so headers reference environment variables and the workflow execution step includes the required env mappings.

Frequently Asked Questions about http_mcp_headers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent GitHub Actions secrets from leaking in HTTP MCP headers?

GitHub Actions secrets in HTTP MCP headers are secured by extracting `${{ secrets.* }}` patterns and converting them into environment variable references. This renders mcp-config.json headers using ${VAR} placeholders and maps the actual secrets securely in the execution step env section.

What is the safest way to configure HTTP MCP servers with repository secrets?

Configuring HTTP MCP servers with repository secrets safely requires using environment variable passthroughs. This generates MCP config header entries with ${VAR} placeholders and adds escaped env values alongside execution-step env mappings that retain default fallbacks and secure secret expressions.

How do I generate an mcp-config.json that uses environment variables for HTTP MCP headers?

Generating an mcp-config.json for HTTP MCP headers involves detecting secret expressions, parsing default fallbacks, and rendering headers with ${VAR} placeholders. An environment passthrough section with escaped values is added to ensure the config file contains no raw secret data.

Can I keep default fallback values when converting GitHub Actions secrets in MCP configs?

Yes, default fallback values are retained when converting GitHub Actions secrets in MCP configs. The extraction process parses fallbacks from the secret expressions and retains them in the execution step env mappings alongside the secure GitHub Actions secret references.

Does Copilot engine workflow support injecting secrets via environment variables for MCP servers?

Copilot engine workflows support injecting secrets via environment variables for MCP servers. During mcp-config.json generation and execution-step preparation, the workflow collects env mappings that securely pass GitHub Actions secret expressions to the HTTP MCP headers.