[PR #251] [MERGED] Feat: Add client header forwarding feature #224

New issue

Closed

opened 2026-10-18 21:12:49 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-18 21:12:49 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/mcpo/pull/251
Author: @rkconsulting
Created: 9/18/2025
Status: ✅ Merged
Merged: 9/24/2025
Merged by: @tjbck

Base: dev ← Head: issues/182/forward-client-http-headers

📝 Commits (2)

b50509d Add client header forwarding feature
086ee45 Merge branch 'dev' into issues/182/forward-client-http-headers

📊 Changes

5 files changed (+670 additions, -385 deletions)

View changed files

➕ CLIENT_HEADER_FORWARDING.md (+151 -0)
📝 src/mcpo/main.py (+13 -2)
➕ src/mcpo/utils/headers.py (+99 -0)
📝 src/mcpo/utils/main.py (+29 -5)
📝 uv.lock (+378 -378)

📄 Description

Pull Request Checklist

Before submitting, make sure you've checked the following:

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

This feature addition enables proper use of mcpo with MCP servers adhering to the MCP June 2025 spec for authentication. mcpo itself does not do any authentication because all MCP servers supporting this already have authentication and session management built in according to the MCP spec. v0.0.15 added support for setting connection-level headers for when mcpo connects to its MCP servers - however, for proper session management we need to continually forward HTTP headers (like the Authorization header forwarded by OWUI tools with the new auth_type system_oauth with every tool call! The MCP spec denotes that this is done via the _meta.headers attribute and the implementation does exactly this. Note that this works for all transport types, even for stdio!

Note: I've added a file CLIENT_HEADER_FORWARDING.md describing the feature - we may want to consolidate this info into the README...?

Changelog entry:

Added tool-call level header forwarding to enable proper MCP-based session and authentication handling

Added

client http header forwarding

Changed

Deprecated

Removed

Fixed

Security

Breaking Changes

Additional Information

Related issues:

Screenshots or Videos

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/mcpo/pull/251 **Author:** [@rkconsulting](https://github.com/rkconsulting) **Created:** 9/18/2025 **Status:** ✅ Merged **Merged:** 9/24/2025 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `issues/182/forward-client-http-headers` --- ### 📝 Commits (2) - [`b50509d`](https://github.com/open-webui/mcpo/commit/b50509d949f6f3d2b713e2a49579ce0eb2f4a972) Add client header forwarding feature - [`086ee45`](https://github.com/open-webui/mcpo/commit/086ee45b39db9823492f7f3144aeb2847f1dda4f) Merge branch 'dev' into issues/182/forward-client-http-headers ### 📊 Changes **5 files changed** (+670 additions, -385 deletions) <details> <summary>View changed files</summary> ➕ `CLIENT_HEADER_FORWARDING.md` (+151 -0) 📝 `src/mcpo/main.py` (+13 -2) ➕ `src/mcpo/utils/headers.py` (+99 -0) 📝 `src/mcpo/utils/main.py` (+29 -5) 📝 `uv.lock` (+378 -378) </details> ### 📄 Description # Pull Request Checklist **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [x] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [x] **Testing:** Have you written and run sufficient tests to validate the changes? - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description This feature addition enables proper use of mcpo with MCP servers adhering to the MCP June 2025 spec for authentication. mcpo itself does not do any authentication because all MCP servers supporting this already have authentication and session management built in according to the MCP spec. v0.0.15 added support for setting connection-level headers for when mcpo connects to its MCP servers - however, for proper session management we need to continually forward HTTP headers (like the Authorization header forwarded by OWUI tools with the new auth_type `system_oauth` **with every tool call**! The MCP spec denotes that this is done via the _meta.headers attribute and the implementation does exactly this. Note that this works for all transport types, even for stdio! Note: I've added a file CLIENT_HEADER_FORWARDING.md describing the feature - we may want to consolidate this info into the README...? Changelog entry: Added tool-call level header forwarding to enable proper MCP-based session and authentication handling ### Added - client http header forwarding ### Changed - ### Deprecated - ### Removed - ### Fixed - ### Security - ### Breaking Changes - --- ### Additional Information Related issues: - #182 - #115 - #226 ### Screenshots or Videos - --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-18 21:12:49 +00:00