Skip to content

feat(webui): allow specifying MCP OAuth 2.0 trusted pivate hosts - #1045

Open
COM8 wants to merge 5 commits into
turnstonelabs:devfrom
COM8:feature/local-mcp-ip-trust
Open

feat(webui): allow specifying MCP OAuth 2.0 trusted pivate hosts#1045
COM8 wants to merge 5 commits into
turnstonelabs:devfrom
COM8:feature/local-mcp-ip-trust

Conversation

@COM8

@COM8 COM8 commented Aug 20, 2026

Copy link
Copy Markdown

Problem Description

In a corporate network Turnstone and for example your local GitLab are running on the same private network. When you now try to configure OAuth for example for the GitLab MCP server, Turnstone blocks this since the GitLab domain resolves to a private network (e.g. gitlab.example.com -> 192.168.1.2).

Changes

  • New optional TURNSTONE_MCP_OAUTH_TRUSTED_PRIVATE_HOSTS environment variable with a list of trusted local IPs.
  • Frontend support for adding additional trusted hosts.
image

In the picture above, you see the settings page with the new oauth_trusted_private_hosts option. The one host with the ENVIRONMENT tag was set via an environment variable. The host with the MANUAL tag was added manually via the webif and can be removed again.

TODOs

  • Test
  • Updated docs

@CLAassistant

CLAassistant commented Aug 20, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@COM8 COM8 changed the title Allow specifying MCP OAuth 2.0 trusted pivate hosts feat(webui): allow specifying MCP OAuth 2.0 trusted pivate hosts Aug 26, 2026
@COM8
COM8 force-pushed the feature/local-mcp-ip-trust branch from c674e3c to be8a45f Compare August 26, 2026 18:58
@COM8
COM8 marked this pull request as ready for review August 27, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants