Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Use your own computers, cloud tools and AI agents from any MCP client with one Frely login.
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.frely.cloud/mcpRun this in your terminal
claude mcp add --transport http frelymcp https://mcp.frely.cloud/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"frelymcp": {
"url": "https://mcp.frely.cloud/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": {
"frelymcp": {
"type": "http",
"url": "https://mcp.frely.cloud/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.frely.cloud/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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 frely.cloud (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
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 1 of 1 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.1.1) reached the registry 11 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, Fomu MCP
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.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
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.
Website · Docs · Frely · English · 简体中文
Frely CLI (frely-cli) gives agents with a shell, such as Claude Code, Codex and pi, the frely Skill: your agent uses your Frely account and the Store from the terminal. For web ChatGPT and Claude, and to work on another computer, it connects a computer you choose to FrelyMCP, so those clients can use the files, shell commands and processes in the folders you allow. The computer connects out to Frely, so you open no ports.
It is also the command line for your Frely account:
127.0.0.1) through to remote clients.Ask an agent that has a shell (Claude Code, Codex, pi) to install the CLI, sign in and install the Skill:
Install Frely CLI and the frely Skill on this computer. On macOS or Linux run curl -fsSL https://frely.cloud/install.sh | sh; on Windows PowerShell run curl.exe -fsSLo "$env:TEMP\frely-install.ps1" https://frely.cloud/install.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File "$env:TEMP\frely-install.ps1". Ask me for my email, run frely login --email <my email>, ask me for the 6-digit code from the email, then run frely login --code <code>. Then run frely skill install --host <your host: claude-code, codex, pi or generic> and read the Skill it installs. Do not run frely link on until I ask for it.
The frely Skill teaches the agent to use your account and to offer FrelyMCP only when a request needs it. This path does not open this computer to remote clients; frely link on does. More
https://frely.cloud/install.sh and install.ps1 only install the program, for scripts and agents that need the CLI. Node.js 22 or newer is needed only for npm.
# macOS / Linux
curl -fsSL https://frely.cloud/install.sh | sh
# Windows (PowerShell)
curl.exe -fsSLo "$env:TEMP\frely-install.ps1" https://frely.cloud/install.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File "$env:TEMP\frely-install.ps1"
Or with npm:
npm install --global --ignore-scripts frely-cli@latest
The installers check the SHA-256 and measure GitHub Releases and npmmirror in parallel and download from the faster one first (npmjs is the last fallback; set FRELY_INSTALL_SOURCES to pin an order). GitHub Releases carry each executable as frely- .gz (use gunzip, or 7-Zip/tar on Windows) with a .sha256 of the decompressed file; the installers do this for you, so prefer them. More
Then sign in and install the Skill for your agent host:
frely login --email <you@example.com> # then: frely login --code <6-digit code>
frely skill install --host
| Command | What it does |
|---|---|
frely skill install --host | Install the frely Skill for an agent host (claude-code, codex, pi or generic). |
frely link on | Turn remote control on: sign in if needed, approve this computer in the browser, start the background service and print the MCP URL. Safe to re-run: it renews expired access and starts a stopped service. |
frely link off | Turn remote control off: revoke access for every client and lock it on this computer, so only frely link on here turns it on again. The background service is uninstalled, or kept running for local Providers. |
frely link status | Show whether remote control is on, off or not enabled yet, with the MCP URL, workspace, expiry and service state. |
frely link workspace add | Share another folder. frely link workspace list shows them all. |
frely doctor | Check sign-in, installation, service and connection. -v for details. |
frely update | Update to the latest version in place. |
frely login / frely logout | Sign in or out of your Frely account. frely login --email then --code signs in without a browser. |
frely sandbox proxy | Forward the command sandbox's network traffic to your own HTTP(S) proxy. Without it the CLI uses HTTPS_PROXY / HTTP_PROXY / ALL_PROXY and, on macOS, the system proxy. --clear removes it. A running background service restarts to apply the change. |
frely tunnel : | Inside a sandboxed command: listen on 127.0.0.1 and forward TCP connections to host:port through the sandbox, for database and redis clients. --local-port N picks the local port. |
frely uninstall | Remove Frely from this computer (lists everything first). |
All commands and options: command reference. frely help --agent --json prints the full machine-readable contract; add --summary for a short grouped index, or a command id or group (for example agent.run, agent) for one command family with examples.
Use FrelyMCP from clients with no shell, such as web ChatGPT and Claude, or to work on another computer.
FrelyMCP is one MCP address for your whole account: https://mcp.frely.cloud/mcp. Every computer with remote control on (frely link on) appears behind it.
If frely is installed, run frely link on. Otherwise the start scripts below install the latest frely and run frely link on for you; run them again any time to update.
With a browser:
# macOS / Linux
curl -fsSL https://frely.cloud/start.sh | sh
# Windows (PowerShell)
curl.exe -fsSLo "$env:TEMP\frely-start.ps1" https://frely.cloud/start.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File "$env:TEMP\frely-start.ps1"
The browser opens to sign in (new accounts can register there) and to approve this computer, then the MCP URL is printed. The workspace is ~/Frely by default (created for you); set FRELY_WORKSPACE=/path to share another folder. When an AI client needs a folder outside it, you can allow that folder on the web. More
On a server (no browser): get a one-time install command on the Frely website (My Devices → Add a computer → Create install command), or ask ChatGPT or Claude connected to FrelyMCP to add a computer. Paste it on the server:
curl -fsSL https://frely.cloud/start.sh | FRELY_INSTALL_TOKEN=fit_... sh
It signs in to your account and turns remote control on without a browser. The token works once and expires after 15 minutes. On Linux, run sudo loginctl enable-linger $USER so the service stays online after you log out of SSH. More
https://mcp.frely.cloud/mcp as a remote MCP server with OAuth:claude mcp add --transport http frely "https://mcp.frely.cloud/mcp", then open /mcp to authorize.To check the connection, ask the client to list the top-level names in your workspace. To stop it, run frely link off on that computer.
list_devices, then read, edit_file, process and web_fetch on the computer you pick, plus your account through frely_list and frely_call. Morefrely link local list); each stays hidden until you turn it on in Frely. Morefrely link on --days 1..365 renews early. The URL never changes. Morefrely agent local add downloads an Agent's repository into its own folder and frely agent local start runs it inside the Frely sandbox. It can write only that folder, cannot read your SSH or cloud credentials, and never sees your Frely API key; its model calls go through a local proxy that adds the key. It can reach Frely's API and, after you approve each one once, the sites its frely.yaml lists. To let your own FrelyMCP call one that serves A2A on a loopback port, use frely service share --type a2a --port --label agent- . Detailsfrely task add [--model ] -- defines a command that runs inside the Frely sandbox; frely task start --wait runs it in its own worker that survives a closed terminal or a reconnect, and --cron runs it on a schedule through the background service, and frely task share offers it as an A2A service. Detailsfrely item install --host claude-code installs an Agent as a local Skill; frely agent run calls it. Morefrely item install --host claude-code (the same command installs Agents too; add @3 for version 3). Paid parts install only when your account holds a pass. frely item update lists installed items that have a newer version; it changes nothing until you run frely item update . Morefrely service share model ollama publishes a local model server's models and prints the AccessPoint made for each one (price 0 until you set it; put it in a Plan to sell it). A model endpoint on your private network works too (--url http://192.168.1.20:3000/v1 --key-stdin; you confirm the address in a terminal). To use a model only from tasks on this computer, register it with frely provider add instead. Morefrely share 3000 asks first, then prints a private link to http://127.0.0.1:3000 through Frely's relay until you press Ctrl+C or it expires (at most 24 hours). Relay traffic is a plan allowance per UTC week; direct connections are not counted. Not the same as frely service share model (local models) or frely tunnel (inside the command sandbox).frely api list|describe|call. MoreFile tools stay inside the shared workspaces and protect credential and shell start-up files. Commands run as your OS user inside an OS sandbox, and are refused where the computer cannot sandbox them. Clients hold OAuth tokens; the CLI keeps its own key in the system credential store. Is it safe? · Sandbox and permissions · Credential storage
Only the beginning is shown; read the rest in the repo