Skip to main content
ThornGuard is not Claude-only. It works today with most developer-managed MCP clients that support either a remote MCP URL plus custom headers or a local bridge command.

​
Current Support Model

ThornGuard works best today with one of these patterns:
  • Direct remote HTTP setup with a URL and custom headers
  • Local stdio bridge such as mcp-remote that connects to ThornGuard on the client’s behalf
The current public deployment still relies on:
  • x-thornguard-license for ThornGuard auth
  • x-mcp-target-url for upstream routing
OAuth / JWT support exists as an additive path, but it is deployment-configured and is not the default public onboarding flow today.

​
Compatibility Snapshot

Platform / ModeWorks TodayNotes
VS Code / CopilotYesBest current fit for direct remote setup with http/sse, headers, and secure inputs/env support
CursorYesGood fit for remote URL + headers, environment-backed variables, and dynamic registration
ZedYesGood fit for custom MCP servers with url, headers, and tool permission controls
Claude DesktopYes, via bridgeCommonly used through mcp-remote
Native OAuth-only remote connector flowsPartialNot yet first-class until ThornGuard stops depending on client-supplied x-mcp-target-url and fully productizes OAuth-based onboarding
Protecting an MCP server you operateYes, with setupSupported today by routing clients through ThornGuard first

​
Direct HTTP Setup

Use this when your client lets you configure:
  • a remote MCP URL
  • custom headers
  • optional environment-backed secrets
This is the cleanest current setup for editors such as VS Code and other header-capable clients.

​
Local Bridge Setup

Use this when your client expects to launch a local command instead of talking directly to a remote HTTP MCP server. This is the common pattern for Claude Desktop today.

​
Security Notes

  • Prefer secret inputs, environment files, or keychain-backed storage over hardcoded tokens in config files.
  • Local bridge tools may log CLI-passed headers before traffic reaches ThornGuard.
  • ThornGuard sanitizes secrets in its own audit trail and webhook deliveries, but it cannot sanitize logs emitted locally by the MCP client or bridge tool.

​
If You Operate the Upstream Service

If you are protecting an MCP service you own, see Protect Your MCP Server.