DevSpace
A self-hosted MCP server that gives ChatGPT and other clients access to code on your machine: read, edit, search and run commands
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Gives the connected client arbitrary command execution on your machine
- Exposes local folders outward through a tunnel
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/devspaceDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
This entry is high risk, so there is no one-click install. Review the code and add the config by hand.
Run in a terminal
claude mcp add --transport http devspace https://your-tunnel-host.example.com/mcpOr add to the file .mcp.json, in the project
{
"mcpServers": {
"devspace": {
"type": "http",
"url": "https://your-tunnel-host.example.com/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"devspace": {
"url": "https://your-tunnel-host.example.com/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Run in a terminal
code --add-mcp '{"name":"devspace","type":"http","url":"https://your-tunnel-host.example.com/mcp"}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"devspace": {
"type": "http",
"url": "https://your-tunnel-host.example.com/mcp"
}
}
}If the file already exists, add the server inside the servers key.
Run in a terminal
codex mcp add devspace --url https://your-tunnel-host.example.com/mcpOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.devspace]
url = "https://your-tunnel-host.example.com/mcp"If the file already exists, append the block to the end.
Run in a terminal
gemini mcp add -s user -t http devspace https://your-tunnel-host.example.com/mcpOr add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"devspace": {
"httpUrl": "https://your-tunnel-host.example.com/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"devspace": {
"serverUrl": "https://your-tunnel-host.example.com/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"devspace": {
"type": "streamableHttp",
"url": "https://your-tunnel-host.example.com/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"devspace": {
"type": "streamable-http",
"url": "https://your-tunnel-host.example.com/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"devspace": {
"type": "remote",
"url": "https://your-tunnel-host.example.com/mcp"
}
}
}If the file already exists, add the server inside the mcp key.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"devspace": {
"url": "https://your-tunnel-host.example.com/mcp"
}
}
}If the file already exists, add the server inside the context_servers key.
Install the CLI: npm install -g @waishnav/devspace, then devspace init and devspace serve. Connect the MCP client to the public /mcp URL and confirm with the owner password.
Other ways from the author
npm install -g @waishnav/devspace
devspace initAfter setup start your tunnel and devspace serve. Requires Node 22.19 or newer.
This is third-party code. Review the repository files before installing.
What it does
DevSpace is an MCP server you run yourself and expose through your own tunnel. Through it ChatGPT or another MCP client gets tools to work with your local projects: read and edit files, search code, inspect directories and run commands for tests, builds, git and package scripts. Access is limited to folders you allow, and the connection is confirmed with an owner password from ~/.devspace/auth.json. It supports isolated git worktrees for parallel sessions, reading instructions from AGENTS.md and CLAUDE.md, and connecting selected agents as subagents. Nothing is uploaded to a third-party service; the code stays on your machine.
Who it is for. For developers who want to run a coding session from ChatGPT or another MCP client directly in their local projects.
Good fit when
- You want ChatGPT to work with real project files on your machine
- You need one MCP endpoint for several clients and short coding sessions
- You need parallel sessions in isolated git worktrees
Not a fit when
- You cannot expose the machine through a tunnel or run arbitrary commands on it
- You have no public HTTPS address and are not ready to set up a tunnel
Example request
Open my project in an allowed folder, find the failing test and propose a fixLimitations
DevSpace grants the connected client serious powers on the machine, including shell command execution inside the opened workspace, so treat the client as a trusted partner with system access. You need your own public HTTPS address through Cloudflare Tunnel, ngrok, Pinggy, Tailscale Funnel or another proxy, and Node 22.19 or newer. Keep the owner password from ~/.devspace/auth.json private. The main client, ChatGPT, is unavailable from Russia without a VPN, so that scenario needs service access.
How to disable. Stop the devspace serve process and the tunnel, remove the connector in the client and, if needed, uninstall the global @waishnav/devspace package and the ~/.devspace/ folder.
MCP
- Transport
- http
- Authentication
- not required
Security check
- Gives the connected client arbitrary command execution on your machine
- Exposes local folders outward through a tunnel
README in short
The README describes DevSpace as an MCP server you keep on your machine and expose through your own tunnel so a client like ChatGPT can work with local code. Installation is via npm or npx, and devspace init asks where you will connect from and which folders and agents are allowed. One /mcp endpoint supports both the newer per-request protocol and older clients without a mode switch. The connection is confirmed with an owner password, and the client gets rights to read, edit, search and run commands in the opened folder. It needs Node 22.19 or newer and supports Linux, macOS and Windows.
FAQ
Is the code uploaded anywhere?
No. The server runs on your machine, the client connects to it through your tunnel, and files stay local.
Is it only for ChatGPT?
No. It is a standard MCP server that other MCP clients connect to, and selected agents can act as subagents.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything