Skip to content

Conversation

@MQ37
Copy link
Contributor

@MQ37 MQ37 commented Jan 22, 2026

Fixes issue #324 where only the first HTTP header was forwarded to
custom MCP actors through the Apify MCP proxy service.

Changes:

  • Extract custom headers from incoming HTTP requests in actor server
  • Pass custom headers through MCP protocol via _meta field
  • Update connectMCPClient to accept optional customHeaders parameter
  • Modify SSE and StreamableHTTP transports to forward custom headers
  • Add customHeaders field to InternalToolArgs type
  • Pass custom headers through tool execution chain

This allows users to pass multiple authentication tokens and custom
headers to their actorized MCP servers, enabling multi-service
authentication and other use cases requiring custom headers.

Closes #324

Fixes issue #324 where only the first HTTP header was forwarded to
custom MCP actors through the Apify MCP proxy service.

Changes:
- Extract custom headers from incoming HTTP requests in actor server
- Pass custom headers through MCP protocol via _meta field
- Update connectMCPClient to accept optional customHeaders parameter
- Modify SSE and StreamableHTTP transports to forward custom headers
- Add customHeaders field to InternalToolArgs type
- Pass custom headers through tool execution chain

This allows users to pass multiple authentication tokens and custom
headers to their actorized MCP servers, enabling multi-service
authentication and other use cases requiring custom headers.

Closes #324
@github-actions github-actions bot added the t-ai Issues owned by the AI team. label Jan 22, 2026
@MQ37 MQ37 marked this pull request as draft January 27, 2026 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-ai Issues owned by the AI team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Forward headers to Actorized MCP Server

3 participants