Model or dataset
Waishnav/devspace avatar
Waishnav/devspace

DevSpace puts an MCP server on your machine and makes the tunnel your problem

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

5,504 stars624 forksTypeScriptMIT

At a glance

What is it?
DevSpace is a self-hosted MCP server that hands a chat client file, search and shell tools inside local folders you approve, reached over an HTTP endpoint you expose yourself. The interesting parts are the two binaries you get, the Host allowlist escape hatch in the example configuration, and the Owner password approval.
Who is it for?
DevSpace is worth setting up if you want one agent client to work across your own repositories and you are the kind of person who reads an environment file before pasting it. Read `.env.example` first, because a single `*` in `DEVSPACE_ALLOWED_HOSTS` disables Host header allowlist protection, and if you set `DEVSPACE_OAUTH_ALLOWED_REDIRECT_HOSTS`, check that it covers the client you actually use, since its example value names only chatgpt.com.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 14 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Waishnav/devspace5,504 ★ · +778
Star history
Repository2026-09-142026-11-15
Waishnav/devspace4.7k5.5k

778 Stars in the last 62 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

One npm install puts two executables on your PATH, and only one is ever named

The `bin` map in `package.json` registers two launchers. `devspace` points at `bin/devspace.js` and `devspace-agentd` points at `bin/devspace-agentd.js`. Every command the documentation ever shows you belongs to the first one: `devspace init`, `devspace serve`, `devspace doctor`. The second one does not appear in the install steps or the platform table. It still installs, because `files` ships `bin` in full, alongside `dist`, `examples`, `schema`, `scripts` and `skills`. That leaves a daemon-shaped binary on your machine with no documented flags, no documented purpose, and no entry in any page the project links to. If something in your workflow ever invokes it, the repository gives you no reference for what it opens or what it needs permission for. The gap is easy to miss precisely because the commands you were told to run all work.

Version identification has a matching loose end. The checked-in `package.json` carries version `1.1.1`, the three newest release tags are `v1.1.1`, `v1.1.0` and `v1.1.0-beta.6` from late October 2026, and the last push to the repository was on 2026-11-01. `packageManager` asks for `[email protected]` for anyone working in the repository, while every documented consumer path uses npm, so contributors and users are on two different package managers by design.

postinstall rewrites node-pty permissions before you run a command

The `scripts` block in `package.json` declares no `postinstall` step; it covers build, dev, test, typecheck, lint and qa. The README's primary install path is an installer script that uses a compatible Node or downloads Node 24 LTS for DevSpace alone, installs without `sudo`, and starts `devspace init`. `scripts` is in the `files` array, so the repository's scripts land on disk and you can read them after installing.

bash
npm install -g @waishnav/devspace

The Node engine range has a ceiling, so Node 27 is out of range on paper

The requirement is written the unusual way round. Both the install section and the `engines` field say `>=22.19 <27`, which closes the top as well as the floor. Most packages declare a minimum and stop. Here a newer runtime is outside the declared range even though nothing in the description suggests the code needs a ceiling, and npm treats an engine mismatch as a warning rather than a refusal, so nothing stops at install time. You find out later, from a warning you have already scrolled past. The floor is just as specific: 22.18 is out, 22.19 is in. For a project that installs globally on developer machines, that combination means the set of hosts where it is unambiguously supported is narrower than the single number the version range suggests.

The example environment file is more permissive than the defaults it sits next to

Read `.env.example` before copying it. `DEVSPACE_WIDGETS=changes` is set there, matching the comment that says the values are off, changes or full and that it defaults to changes. `DEVSPACE_LOG_SHELL_COMMANDS=0` sits beside `DEVSPACE_LOG_TOOL_CALLS=1`, which means the log records that a tool ran without recording what it ran. And the commented-out optional `DEVSPACE_OAUTH_ALLOWED_REDIRECT_HOSTS=chatgpt.com,localhost,127.0.0.1` example names one remote client, while the project description lists ChatGPT, Claude, Hermes, Grok Bot and OpenClaw.

One asterisk switches off the Host header allowlist that the base URL normally derives

The default posture here is derived, not hardcoded, and that is the sensible design. Set `DEVSPACE_PUBLIC_BASE_URL` and the inbound Host allowlist is derived from it, which is the right shape for a tunnel whose hostname changes every time you start it. The escape hatch is a single character: the comment on `DEVSPACE_ALLOWED_HOSTS` says that `*` disables Host header allowlist protection. The difference between the two states is whether the server checks that the hostname a request arrived with is the one you declared, and between them there is one environment variable. That variable is not needed for the documented setups, which all name a specific tunnel host, so setting it is a decision to remove a check rather than a convenience.

The setup question decides whether a public endpoint exists at all

The first thing `devspace init` asks is where you will use DevSpace, and the answer changes the shape of the deployment. To also serve an MCP host, setup takes the allowed roots and a public URL, for example `--public-url` and `--roots`, from a tunnel such as Cloudflare Tunnel, ngrok, Pinggy, Tailscale Funnel, or your own HTTPS reverse proxy. You then run `devspace serve` and connect the client to your public `/mcp` URL, which puts an internet-reachable endpoint in front of your machine. For subagents only, `devspace init --yes` sets things up, no server, tunnel, or OAuth is needed, and subagents run with your local user's authority, scoped to the project they are started from.

text
http://127.0.0.1:7676/mcp

The Owner password lives in two places, and its refresh token lasts thirty days

The approval gate is described in three sentences. When the client connects, DevSpace opens an Owner password approval page, you enter the Owner password generated by `devspace init`, and the same password is stored in `~/.devspace/auth.json`, with a request to keep it private. The environment variable form, `DEVSPACE_OAUTH_OWNER_TOKEN`, is annotated for non-interactive or fully env-driven deployments and ships as a placeholder. So the secret ends up in a dotfile in your home directory and, in that second mode, in whatever your deployment reads. The same file shows commented-out optional OAuth tuning with example values of 3600 seconds for access tokens, 2592000 seconds (thirty days) for refresh tokens, and the scope `devspace`. With those values, a valid refresh token would carry a month of access without anyone typing anything. Note also that your account, not this tool, is what your provider's terms govern; the project says so plainly in its usage note.

text
~/.devspace/auth.json

No protocol flag exists, because the same /mcp endpoint answers both client generations

Protocol negotiation happens at the endpoint rather than in your configuration. One `/mcp` endpoint serves the 2026-07-28 protocol and older 2025-era clients without any configuration. The benefit is real: there is no version flag to set wrongly, and no way to accidentally pin yourself to an old client dialect. You cannot find out by reading configuration, because there is nothing to configure. Setup takes the public origin without the `/mcp` suffix and adds the path afterwards, which is one more value to keep straight when you are copying a URL between the setup prompt and your client.

Editorial conclusion

DevSpace is worth setting up if you want one agent client to work across your own repositories and you are the kind of person who reads an environment file before pasting it. Read `.env.example` first, because a single `*` in `DEVSPACE_ALLOWED_HOSTS` disables Host header allowlist protection, and if you set `DEVSPACE_OAUTH_ALLOWED_REDIRECT_HOSTS`, check that it covers the client you actually use, since its example value names only chatgpt.com. The tunnel is the real exposure, so keep it temporary.

Frequently asked questions

What is DevSpace?

It is a self-hosted MCP server that lets a chat client read, edit, search and run code inside local project folders you approve. It runs on your machine, listens on http://127.0.0.1:7676/mcp by default, and is reached over an HTTP endpoint you expose through a tunnel you control.

Is DevSpace free to use?

The package is published under the MIT licence and the platform table, documentation and support files all come with it. The one commercial arrangement named in the project is a sponsorship slot, currently commented out in the README, offering cash back for an optional sponsored footer in a coding agent.

how to use devspace

Install with the `curl -fsSL https://devspace.run/install | sh` installer or `npm install -g @waishnav/devspace` followed by `devspace init`, then answer the two setup questions about where you will use it and which agents may act as subagents. Start `devspace serve`, point your client at the public `/mcp` URL, approve with the Owner password stored in `~/.devspace/auth.json`, and `devspace doctor` checks the local setup.

what is claude devspace

The repository does not define that phrase, but Claude appears in documented places. The README lists Claude as an MCP host and Claude Code as a subagent, and `DEVSPACE_SKILL_PATHS` in the example environment file points at a .claude/skills folder alongside a .codex one, so skills on disk are discovered from both.

devspace vs devcontainer

The repository makes no comparison, and there is no Dockerfile at the top level and no image or compose file. DevSpace is an MCP server plus a tunnel plus an allowlist of local roots, so it does not build or reproduce an environment.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. Waishnav/devspace on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/waishnav-devspace.svg)](https://hysenlabs.com/projects/waishnav-devspace)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/waishnav-devspace.svg)](https://hysenlabs.com/projects/waishnav-devspace)

Was this useful?