KHOSAN_DevSpace
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
KHOSAN_DevSpace
Private, tool-only MCP runtime profiles built around a pinned DevSpace core.
Repository: kongsak4807017/KHOSAN_DevSpaceMCP
This repository does not replace the live legacy instance yet. The legacy service remains on 127.0.0.1:7676. The first V2 canary is a loopback-only local profile on 127.0.0.1:7678 for Codex desktop, CLI, and IDE clients.
Why this exists
The previous wrapper mixed UI, tunnel control, process ownership, secrets, and health polling. It also probed the public MCP endpoint every three seconds, producing hundreds of thousands of log records. This implementation separates:
reproducible DevSpace dependency and profiles;
runtime secrets and SQLite state;
failure classification;
single-owner process supervision;
bounded logs;
ChatGPT web and local Codex access paths.
Related MCP server: CodePier
Archetype
tool-only / private internal. DevSpace supplies the MCP tools. No widget is added because the requested workflow does not need a custom UI.
Current status
Pinned DevSpace:
1.0.8Local profile:
127.0.0.1:7678Web profile: template only; it needs a separate stable HTTPS canary origin before activation
Legacy profile: unchanged at
127.0.0.1:7676Subagents: disabled in both V2 profiles
Commands
npm ci
npm run test:strict
npm run compile
./scripts/ops.ps1 materialize local
./scripts/ops.ps1 doctor local
./scripts/ops.ps1 start local
./scripts/ops.ps1 status local
./scripts/ops.ps1 classify local --forbiddenstart owns a profile lock, restarts failed child processes with capped exponential backoff, opens a circuit after repeated crashes, and writes rotating logs under the ignored runtime/ directory.
Codex local registration
codex mcp add KHOSAN_DevSpace --url http://127.0.0.1:7678/mcp
codex mcp login KHOSAN_DevSpaceOAuth requires the generated Owner password stored in the ignored local profile auth file. Enter it only in the loopback approval page; do not paste it into chat or logs. Restart the Codex client after authentication so its MCP inventory refreshes.
Documentation
Primary references
Production readiness
The loopback local canary is implemented and validated. The separate ChatGPT web profile is intentionally not active until it has its own stable HTTPS origin and the dependency exception in docs/SECURITY_BOUNDARY.md is resolved or explicitly accepted.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.
Secure and manage MCP servers through the Speakeasy AI Control Plane from your agent.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT and Claude to securely connect to existing Codex sessions across local and remote development hosts via a self-hosted MCP gateway.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceConnects ChatGPT and MCP clients to authorized local development environments, enabling secure file access, shell execution, persistent tasks, browser/desktop control, and remote management of projects.19MIT
- FlicenseNot gradedqualityAmaintenanceExposes an OAuth-gated MCP endpoint with 38 governed tools that let web-based AI chat clients read and edit local files, run whitelisted shell commands, search, use Git and SQLite, fetch localhost/intranet APIs, automate Chromium and DevTools, and manage background tasks, ports, clipboard, notifications, and Postman. Local IDEs can connect directly over 127.0.0.1, while remote clients reach the same machine through a secure public ingress.-
- AlicenseNot gradedqualityAmaintenanceExposes a governed suite of 38 OAuth-gated tools over one MCP endpoint, letting web-based AI chat clients read and edit files, run whitelisted shell commands, search, and use Git, SQLite, browser automation, DevTools, background tasks, ports, clipboard, notifications, and localhost services on the user's own machine. It also allows local IDEs and automation tools to connect directly over localhost for offline, low-latency access.MIT