lws-mcp
# lws-mcp
[](https://github.com/NKSTUD/lws-mcp/actions/workflows/ci.yml)
[](LICENSE)
[](https://pypi.org/project/lws-mcp/)
[](pyproject.toml)
**English** · [Français](README.fr.md)
An [MCP](https://modelcontextprotocol.io) server for the [LWS](https://www.lws.fr) 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](https://api.lws.fr/api-client/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.
<!-- mcp-name: io.github.NKSTUD/lws-mcp -->
## Tools
| 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`, `@`).
## Safety
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:
- **Purchases are off by default.** `buy_hosting` and `renew_hosting` only exist when `LWS_ENABLE_PURCHASES=true`.
- **Read-only mode.** `LWS_READ_ONLY=true` removes every tool that changes something.
- **Hints for your client.** Every tool declares whether it reads, writes or destroys ([tool annotations](https://modelcontextprotocol.io/specification/2025-06-18/server/tools#tool-annotations)), so clients can ask before running it.
- **Test environment.** `LWS_TEST_MODE=true` sends every request to the LWS sandbox.
- **Your key stays local.** It goes only to `api.lws.net`, and is never logged or returned to the model.
## Requirements
- An LWS account and its API key: [LWS Panel](https://www.lws.fr/panel) → your account number (LWS-XXXXXX, top right) → **Api LWS** → **Clé API en mode PRODUCTION** → *voir*. [LWS guide](https://aide.lws.fr/a/1943).
- The public IP address of the machine running the server, allowed on the same **Api LWS** page. Otherwise every call fails with `bad source <your IP>`.
- [uv](https://docs.astral.sh/uv/getting-started/installation/) (it fetches Python and the server for you).
## Installation
Every client runs the same command, `uvx lws-mcp`, with `LWS_LOGIN` and `LWS_API_KEY` in its environment (see [Configuration](#configuration) for the optional settings).
[](https://cursor.com/en/install-mcp?name=lws&config=eyJjb21tYW5kIjoidXZ4IiwiYXJncyI6WyJsd3MtbWNwIl0sImVudiI6eyJMV1NfTE9HSU4iOiIiLCJMV1NfQVBJX0tFWSI6IiJ9fQ%3D%3D)
[](https://insiders.vscode.dev/redirect/mcp/install?name=lws&config=%7B%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22lws-mcp%22%5D%2C%22env%22%3A%7B%22LWS_LOGIN%22%3A%22%22%2C%22LWS_API_KEY%22%3A%22%22%7D%7D)
The buttons leave `LWS_LOGIN` and `LWS_API_KEY` empty: fill them in after installing.
<details open>
<summary><b>Claude Code</b></summary>
```bash
claude mcp add lws \
-e LWS_LOGIN=123456 \
-e LWS_API_KEY=your-api-key \
-- uvx lws-mcp
```
</details>
<details>
<summary><b>Codex</b> (CLI, IDE extension and app)</summary>
```bash
codex mcp add lws \
--env LWS_LOGIN=123456 \
--env LWS_API_KEY=your-api-key \
-- uvx lws-mcp
```
Or in `~/.codex/config.toml`:
```toml
[mcp_servers.lws]
command = "uvx"
args = ["lws-mcp"]
env = { LWS_LOGIN = "123456", LWS_API_KEY = "your-api-key" }
```
</details>
<details>
<summary><b>Cursor</b></summary>
Use the button above, or add to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (one project):
```json
{
"mcpServers": {
"lws": {
"command": "uvx",
"args": [
"lws-mcp"
],
"env": {
"LWS_LOGIN": "123456",
"LWS_API_KEY": "your-api-key"
}
}
}
}
```
</details>
<details>
<summary><b>VS Code</b> (GitHub Copilot)</summary>
```bash
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`:
```json
{
"servers": {
"lws": {
"type": "stdio",
"command": "uvx",
"args": [
"lws-mcp"
],
"env": {
"LWS_LOGIN": "123456",
"LWS_API_KEY": "your-api-key"
}
}
}
}
```
</details>
<details>
<summary><b>Claude Desktop · Windsurf · Gemini CLI · others</b></summary>
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 |
```json
{
"mcpServers": {
"lws": {
"command": "uvx",
"args": [
"lws-mcp"
],
"env": {
"LWS_LOGIN": "123456",
"LWS_API_KEY": "your-api-key"
}
}
}
}
```
</details>
## Configuration
| 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. |
## Good to know
- **Deferred actions.** Nameserver changes, transfer protection, auth codes, purchases and renewals are processed in the background. Follow them with `list_pending_requests`.
- **Propagation.** A DNS change can take from minutes to a few hours to be seen everywhere: each resolver keeps the old answer until its TTL runs out. `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.
- **Record ids change.** LWS replaces a record under a new id when it is updated. `add_dns_record` and `update_dns_record` return the current id.
- **Rate limit.** LWS refuses bursts of requests (about fifteen in a row) with `Invalid input (rate limit)`: wait a minute and retry.
- **Allowed TTLs.** 900, 1800, 3600, 7200, 21600, 43200 or 86400 seconds.
## Development
```bash
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](https://github.com/modelcontextprotocol/inspector), credentials in a local `.env` (see [.env.example](.env.example)):
```bash
npx @modelcontextprotocol/inspector uv run --env-file .env lws-mcp
```
See [CONTRIBUTING.md](CONTRIBUTING.md) to add a tool or fix a bug.
## License
[MIT](LICENSE)
TDQS
Scored across 26 tools
Most tools target a distinct resource and action, and descriptions clearly separate DNS zone inspection from propagation checks, contacts, hostings, and account/request operations. Minor overlap exists between add_dns_record and update_dns_record (upsert behavior) and between list_requests and list_pending_requests, but the descriptions largely resolve these.
All tool names use consistent snake_case with a verb-noun pattern (get_, list_, create_, update_, delete_, set_, check_, request_). The convention is predictable across every resource area.
26 tools is on the heavy side for an MCP surface; while the LWS domain is broad and each operation is granular, several tools could be consolidated (e.g., request listings, price lookups). The count is borderline rather than clearly excessive given the multi-service scope.
Core lifecycle operations are missing: there are no tools to register/renew/delete a domain, purchase/renew/delete a hosting, or delete a contact. The gap is especially pronounced because get_renewal_prices explicitly references renew_hosting, which does not exist, creating a dead end.