Skip to content

Devspace

Minimal Coding Agent Harness on MCP for ChatGPT, Claude, Hermes, Grok Bot, OpenClaw

Install

$npx @waishnav/devspace init
Claude Code
claude mcp add devspace -- npx @waishnav/devspace init
Cursor / Claude Desktop (mcp.json)
{
  "mcpServers": {
    "devspace": {
      "command": "npx",
      "args": [
        "@waishnav/devspace",
        "init"
      ]
    }
  }
}

Install command taken from the project's README or registry entry. Always review code before running it.

DevSpace

Bring a Codex-style coding workflow to ChatGPT.

Give ChatGPT a secure connection to your own machine and Turn ChatGPT into Codex

DevSpace is a self-hosted MCP server that lets ChatGPT read, edit, search, and run code in your real local projects — your files, your tools, your terminal — without uploading anything to a third party. You run it on your machine, expose it through a tunnel you control, and approve the connection with a password only you have.

The same /mcp endpoint serves the 2026-07-28 per-request protocol and automatically supports older 2025-era clients through stateless compatibility handling. There is no protocol mode to configure.

Sponsors and Special Thanks

DevSpace is open to new sponsors. Get in touch to become one.

Installation

DevSpace requires Node >=22.19 <27.

Install the DevSpace CLI:

npm install -g @waishnav/devspace

Then initialize DevSpace:

devspace init

Or run it without a global install:

npx @waishnav/devspace init

During setup, DevSpace asks for:

  • where you will use it: ChatGPT, Coding Agents, or both
  • which agents DevSpace may use as subagents

The first choice is where you invoke DevSpace from. The subagent choice is separate: ChatGPT or another coding agent can delegate work through DevSpace to the agents you select there.

If you select ChatGPT, setup also asks which local project folders it may open and for your public HTTPS base URL from Cloudflare Tunnel, ngrok, Pinggy, Tailscale Funnel, or another reverse proxy. A Coding Agents-only setup asks neither question: local commands use the current Git project, or the current directory outside a repository.

Use the public origin without /mcp during setup:

https://your-tunnel-host.example.com

You will configure your MCP client with the public /mcp URL after setup. Run devspace serve when using ChatGPT. For Coding Agents, setup prints a skills command and lets the Skills CLI handle installation.

When the client connects, DevSpace opens an Owner password approval page. Enter the Owner password printed by devspace init. It is also stored in:

~/.devspace/auth.json

Keep that password private.

Connect Your MCP Client

The default local endpoint is:

http://127.0.0.1:7676/mcp

Most users should connect through a public HTTPS tunnel:

https://your-tunnel-host.example.com/mcp

[!NOTE] Using DevSpace as an MCP connector isn't against OpenAI's Usage Policies — it's a standard custom App/connector setup, and writing or running code isn't a restricted use case. But your account is governed by your usage, not by DevSpace. Don't point it at anything that would violate your provider's terms. Used normally, you're fine. (Based on OpenAI's Usage Policies and Service Terms as of June 2026.)

What ChatGPT Can Do

Once connected, ChatGPT can open one of your approved project folders as a workspace. From there, it can inspect the repo, make scoped edits, run commands, and show you what changed.

DevSpace gives ChatGPT tools to:

Similar plugs

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype…

A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io

Explore related