Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
A cloud Linux desktop for your AI: browse, click, type, read the screen and run commands.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.box.simular.ai/mcpRun this in your terminal
claude mcp add --transport http box https://mcp.box.simular.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"box": {
"url": "https://mcp.box.simular.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"box": {
"type": "http",
"url": "https://mcp.box.simular.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.box.simular.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain simular.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 255 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, AI Deprecations
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
box gives your AI agent a computer of its own: a cloud Linux desktop with Chrome and a shell that it drives over MCP, while your own computer stays free. You can watch it live and take over at https://box.simular.ai/box.
Most agents need no plugin: add the MCP server https://mcp.box.simular.ai/mcp and sign in once (see https://box.simular.ai/install). This repository holds a package for each agent that installs box its own way. Each folder stands alone and is released through that agent's channel.
| Agent | Folder | Sign-in | Install |
|---|---|---|---|
| Claude Code and Cowork | claude/ | OAuth, once in the browser | /plugin marketplace add simular-ai/box-plugin, then /plugin install box@simular-box |
| DeepSeek Harness (dsh) | dsh/ | Personal key (cb_...), pasted on the plugin's page in Plugins | dsh/README.md |
| Any of Claude Code, Codex, Cursor, OpenCode, Gemini CLI, Hermes, OpenClaw, VS Code (and steps for Claude Desktop) | cli/ | OAuth; personal key with --auth key for Hermes and OpenClaw | npx @simular-ai/box connect (check with npx @simular-ai/box doctor) |
| Hermes Agent | hermes/ | Personal key (cb_...) in MCP_BOX_API_KEY; OAuth optional | hermes/README.md |
Going offline in the middle of a task? In Claude Code with the plugin, /box:offload hands the task to a fresh Claude Code (or Codex, Cursor) session in your box, which keeps working while you are away; /box:back brings its commits and its written hand-over home and merges them. Any other agent or a plain terminal uses npx @simular-ai/box offload and npx @simular-ai/box back. Setup and details: cli/README.md.
Add a folder named after the agent with its own manifest, MCP config and, where the agent supports skills, a copy of claude/skills/box/SKILL.md. Point it at https://mcp.box.simular.ai/mcp. Use OAuth sign-in where the agent supports it; otherwise read a personal key from an environment variable or the agent's own credentials store, never from a file in the package. Add a row above.
claude/: bump version in claude/.claude-plugin/plugin.json. Claude Code doesn't auto-update third-party marketplaces: users get it with /plugin marketplace update simular-box and /plugin update box@simular-box, or with npx @simular-ai/box connect.dsh/: bump version in dsh/package.json, then push a tag dsh-vX.Y.Z. The release workflow attaches dsh-box.tgz.hermes/: bump version in hermes/plugin.json. Users copy the folder by hand until box is in the Hermes plugin catalog.cli/: bump version in cli/package.json, then push a tag cli-vX.Y.Z. The publish-cli.yml workflow tests it and publishes @simular-ai/box to npm through trusted publishing (OIDC), with provenance; the one-time npm setup is in cli/README.md. When the box endpoint moves, change DEFAULT_MCP_URL in cli/src/constants.js, add the old host to OLD_HOSTS there, change the URL in every plugin folder, and release each one.