Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Manage LWS (lws.fr) domains, DNS zones, hosting and account from any MCP client.
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.
LWS_LOGIN, LWS_API_KEY, LWS_READ_ONLY, LWS_ENABLE_PURCHASES, LWS_TEST_MODE, LWS_TEST_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"lws": {
"command": "uvx",
"args": [
"lws-mcp"
],
"env": {
"LWS_LOGIN": "your-value",
"LWS_API_KEY": "your-value",
"LWS_READ_ONLY": "your-value",
"LWS_ENABLE_PURCHASES": "your-value",
"LWS_TEST_MODE": "your-value",
"LWS_TEST_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add lws --env LWS_LOGIN=your-value --env LWS_API_KEY=your-value --env LWS_READ_ONLY=your-value --env LWS_ENABLE_PURCHASES=your-value --env LWS_TEST_MODE=your-value --env LWS_TEST_API_KEY=your-value -- uvx lws-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"lws": {
"command": "uvx",
"args": [
"lws-mcp"
],
"env": {
"LWS_LOGIN": "your-value",
"LWS_API_KEY": "your-value",
"LWS_READ_ONLY": "your-value",
"LWS_ENABLE_PURCHASES": "your-value",
"LWS_TEST_MODE": "your-value",
"LWS_TEST_API_KEY": "your-value"
}
}
}
}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": {
"lws": {
"type": "stdio",
"command": "uvx",
"args": [
"lws-mcp"
],
"env": {
"LWS_LOGIN": "your-value",
"LWS_API_KEY": "your-value",
"LWS_READ_ONLY": "your-value",
"LWS_ENABLE_PURCHASES": "your-value",
"LWS_TEST_MODE": "your-value",
"LWS_TEST_API_KEY": "your-value"
}
}
}
}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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
LWS_READ_ONLY envLWS_ENABLE_PURCHASES envLWS_TEST_MODE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 7, 2026
The registry name was verified with the GitHub account NKSTUD, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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.
You need to fill in: LWS_LOGIN, LWS_API_KEY, LWS_TEST_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 22 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
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.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
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.
English · Français
An MCP server for the LWS Client API. Manage your domains, DNS zones, hosting and account from Claude, Cursor or any MCP client:
*"Add the CNAME records Stripe gave me to example.fr, then tell me when they are live."*
It covers the whole LWS Client API (29 endpoints), plus a propagation check that compares your LWS zone, its nameservers and three public resolvers.
Community project, not affiliated with or endorsed by LWS.
| Area | Tools |
|---|---|
| DNS | get_dns_zone · add_dns_record · update_dns_record · delete_dns_record · check_dns_propagation |
| Domains | get_domain · check_domain_availability · list_tlds · update_nameservers · set_transfer_protection · request_transfer_authcode · create_domain_redirect · delete_domain_redirect |
| Hosting | list_hostings · get_hosting · list_hosting_prices · get_renewal_prices · set_auto_renew · buy_hosting¹ · renew_hosting¹ |
| Account | get_account_balance · get_purchase_history · list_contacts · get_contact · create_contact · update_contact · add_test_credit_to_contact² · add_test_credit_to_account² |
| Requests | list_requests · list_pending_requests |
¹ Paid: off unless LWS_ENABLE_PURCHASES=true. ² Only in test mode.
DNS record names can be written in full (_dmarc.example.fr): they are shortened to what the LWS zone expects (_dmarc, @).
An assistant with access to your DNS can take a site or a mailbox down, and one with access to purchases can spend money. So:
buy_hosting and renew_hosting only exist when LWS_ENABLE_PURCHASES=true.LWS_READ_ONLY=true removes every tool that changes something.LWS_TEST_MODE=true sends every request to the LWS sandbox.api.lws.net, and is never logged or returned to the model.bad source .Every client runs the same command, uvx lws-mcp, with LWS_LOGIN and LWS_API_KEY in its environment (see Configuration for the optional settings).
The buttons leave LWS_LOGIN and LWS_API_KEY empty: fill them in after installing.
Claude Code
claude mcp add lws \
-e LWS_LOGIN=123456 \ -e LWS_API_KEY=your-api-key \ -- uvx lws-mcp
</details>
Codex (CLI, IDE extension and app)
codex mcp add lws \
--env LWS_LOGIN=123456 \ --env LWS_API_KEY=your-api-key \ -- uvx lws-mcp
Or in ~/.codex/config.toml:
[mcp_servers.lws]
command = "uvx" args = ["lws-mcp"] env = { LWS_LOGIN = "123456", LWS_API_KEY = "your-api-key" }
</details>
Cursor
Use the button above, or add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": { "lws": { "command": "uvx", "args": [ "lws-mcp" ], "env": { "LWS_LOGIN": "123456", "LWS_API_KEY": "your-api-key" } } } }
</details>
VS Code (GitHub Copilot)
code --add-mcp '{"name":"lws","command":"uvx","args":["lws-mcp"],"env":{"LWS_LOGIN":"123456","LWS_API_KEY":"your-api-key"}}'
Or in .vscode/mcp.json:
{
"servers": { "lws": { "type": "stdio", "command": "uvx", "args": [ "lws-mcp" ], "env": { "LWS_LOGIN": "123456", "LWS_API_KEY": "your-api-key" } } } }
</details>
Claude Desktop · Windsurf · Gemini CLI · others
Add this block to the client's MCP file:
| Client | File |
|---|---|
| Claude Desktop | Settings → Developer → Edit Config (claude_desktop_config.json) |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Gemini CLI | ~/.gemini/settings.json |
| Cline, Roo Code, Zed… | their MCP settings, same format |
{
"mcpServers": { "lws": { "command": "uvx", "args": [ "lws-mcp" ], "env": { "LWS_LOGIN": "123456", "LWS_API_KEY": "your-api-key" } } } }
</details>
| Variable | Default | Description |
|---|---|---|
LWS_LOGIN | *required* | Your LWS account ID (the digits of LWS-XXXXXX). |
LWS_API_KEY | *required* | Production API key. |
LWS_TEST_API_KEY | Test key, used instead of LWS_API_KEY in test mode. | |
LWS_TEST_MODE | false | Send requests to the LWS test environment. |
LWS_READ_ONLY | false | Only expose tools that read. |
LWS_ENABLE_PURCHASES | false | Expose buy_hosting and renew_hosting. |
LWS_TIMEOUT | 30 | Request timeout, in seconds. |
LWS_BASE_URL | https://api.lws.net/v1 | API base URL. |
list_pending_requests.check_dns_propagation compares what is saved in the LWS zone, what the domain's nameservers answer (no cache) and what Cloudflare, Google and Quad9 answer, then says how long a stale answer can last. Some networks block direct DNS queries to nameservers; the resolvers are asked over HTTPS, so that part always works.add_dns_record and update_dns_record return the current id.Invalid input (rate limit): wait a minute and retry.git clone https://github.com/NKSTUD/lws-mcp && cd lws-mcp
uv sync uv run pytest uv run ruff check . && uv run ruff format --check .
Try it against your account with the MCP Inspector, credentials in a local .env (see .env.example):
npx @modelcontextprotocol/inspector uv run --env-file .env lws-mcp
See CONTRIBUTING.md to add a tool or fix a bug.
MIT