Skip to content

Add quilr-web release notes for d7f8ceee5 #54

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bedapudi67 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add quilr-web release notes for d7f8ceee5 #54

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion docs/platform-areas/mcp-gateway.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,13 @@ Use MCP Gateway when you need to:

- View MCP backends and enable or disable them.
- Add a custom MCP with automatic auth probing, OAuth passthrough, or upstream API key injection.
- Install MCPs from the MCP Library.
- Install MCPs from the MCP Library, with server-side search, install-status and auth-type filters,
and pagination for large catalogs.
- Request MCP installs when install permission is not available.
- Configure MCP general settings, guardrails, and tools.
- Create and revoke MCP access tokens for non-OAuth MCPs.
- Enable a trusted user-claims header for non-OAuth MCPs so direct MCP and OneMCP backends can
identify the calling user.
- Configure access control for agent clients, smart groups, and individual users.
- Map agent clients to MCP backends.
- Set per-smart-group and per-user rules that override tool availability and guardrail actions for a
Expand All @@ -54,6 +57,16 @@ Use MCP Gateway when you need to:
requires credentials without OAuth support.
- **No auth:** Used when the MCP does not require credentials.

## User Claims Header

For non-OAuth MCPs (upstream API key or no-auth), a **Send user claims to backend** toggle is
available in the MCP's general settings. When enabled, the gateway adds a trusted `X-User-Claims`
header — containing the authenticated user's subject, email, tenant, and authentication method
when available — to direct MCP and OneMCP requests. Any client-supplied `X-User-Claims` header is
stripped and replaced with the gateway's trusted value. Enabling this setting disables shared
capability caching for the MCP. This setting is not shown for gateway-managed OAuth or OAuth
passthrough MCPs.

## Access Control

Each MCP server has an **Access Control** section in its general settings with three layers of
Expand Down
19 changes: 19 additions & 0 deletions docs/release-notes/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,25 @@ hide_copy_dropdown: true

# Release Notes

## July 13, 2026

### New

- [MCP Gateway](/platform-areas/mcp-gateway): Added a **Send user claims to backend** toggle to the
general settings of non-OAuth MCPs (upstream API key or no-auth). When enabled, the gateway adds
a trusted `X-User-Claims` header — with the authenticated user's subject, email, tenant, and
authentication method when available — to direct MCP and OneMCP requests. Any client-supplied
`X-User-Claims` header is stripped and replaced with the gateway's trusted value, and shared
capability caching is disabled for the MCP while the setting is enabled. This setting is not
available for gateway-managed OAuth or OAuth passthrough MCPs.

### Improved

- [MCP Gateway](/platform-areas/mcp-gateway): The MCP Library now searches and filters the catalog
server-side and paginates results, showing up to 50 MCPs per page with **Previous** / **Next**
controls and a page indicator. Browsing and searching large catalogs is now faster and no longer
limited to what was loaded on the page.

## June 26, 2026

### New
Expand Down