Skip to content

[Feature Request]: Headers passthrough from mcp server configuration #1356

@playground

Description

@playground

@kevalmahajan here it is.

🧭 Type of Feature

Please select the most appropriate category:

  • Enhancement to existing functionality
  • New feature or capability
  • New MCP-compliant server
  • New component or integration
  • Developer tooling or test improvement
  • Packaging, automation and deployment (ex: pypi, docker, quay.io, kubernetes, terraform)
  • Other (please describe below)

🧭 Epic

Title: Headers passthrough from mcp server configuration
Goal: Headers passthrough
Why now: Not yet supported


🙋♂️ User Story 1

As a: I would like to be able to pass in custom headers
I want: Some tools require that information to function
So that:

✅ Acceptance Criteria

Scenario: claude_desktop_config.json
{
  "mcpServers": {
    "open-horizon-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://localhost:4444/servers/224831b6cd344fb6b35179401ee8b7cc/mcp",
        "--header",
        "exchange-org:<orgId>",
        "--header",
        "exchange-url:http://open-horizon.lfedge.iol.unh.edu:3090/v1/orgs",
        "--header",
        "exchange-credential:<your_credential",
        "--header",
        "Authorization:Bearer *****************"
      ]
    }
  }
}

🔗 MCP Standards Check

  • Change adheres to current MCP specifications
  • No breaking changes to existing MCP-compliant integrations
  • If deviations exist, please describe them below:

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requesttriageIssues / Features awaiting triage

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions