MCP server

The LWS MCP server connects an AI assistant to your LWS account. MCP (Model Context Protocol) is the open standard that lets assistants use outside services: you ask, in plain language, to list your domains, read a DNS zone or add a record to it, and the assistant makes the calls to this API for you.

The server is hosted by LWS at https://mcp.lws.net/mcp: nothing to install. Your API key stays with LWS. The assistant gets a token, which you create on the mcp.lws.net portal and can suspend or revoke at any time. Each token has its own tools, lifetime and limits, and every one of its actions is recorded in your logs.

The portal is in French: its labels are given below as they appear, with their meaning.

Before you start

• A production API key, generated from your customer area, as for any call to this API.
• The IP addresses allowed by your API access. The MCP needs two: your internet connection's, to sign in to the portal, and the MCP server's, so that the assistant can act. The portal gives you the latter when you activate the service.
• Prepaid credit, only if the assistant is to buy or renew domains.

Activate the MCP

1. Go to mcp.lws.net and sign in with your LWS ID (the number alone) and your API key. If the sign-in is refused, check both, then the allowed IP addresses: the message gives the one to add.
2. On your first sign-in, accept the terms of use and give the e-mail address for alerts.
3. Confirm that address with the link you receive, valid for 24 hours. Until it is confirmed, no alert is sent. The sender is [email protected].
4. Add the MCP server's IP address to the allowed IPs of your API access, if not done yet.

We also advise you to turn on two-factor authentication, in Mon compte (My account).

Connect your assistant

Two ways, depending on the assistant:

• Claude and ChatGPT connect through authorization (OAuth): the server's address is enough, and the token is created when you give your consent on the portal.
• The others (Claude Code, Cursor, n8n…) use a token you create on the portal, under Jetons (Tokens), which they send in the Authorization: Bearer header. Its value is shown only once: copy it when you create it.

Claude (claude.ai, desktop or mobile app)

1. In Claude, open the connectors (Customize or Settings menu) and add a custom connector.
2. Name: LWS. Address: https://mcp.lws.net/mcp. Leave the rest as it is.
3. Claude opens the portal: sign in, then choose what Claude may do. The portal suggests a read-only token valid for 30 days, which you can adjust under “Réglages avancés” (Advanced settings).

ChatGPT

1. On chatgpt.com, add a custom MCP server (connectors menu, depending on your version). The option depends on your plan and on your workspace's settings.
2. Server address: https://mcp.lws.net/mcp. Authentication: OAuth.
3. ChatGPT opens the portal: sign in, then choose what it may do.

A token obtained through authorization lasts for the lifetime chosen: when it expires, the assistant asks for a new authorization. If the portal shows “Application non vérifiée par LWS” (application not verified by LWS), only go on if you have just started the connection yourself.

Claude Code

In a terminal, replacing VOTRE_JETON with the token's value:

claude mcp add --transport http lws https://mcp.lws.net/mcp --header "Authorization: Bearer VOTRE_JETON"

Cursor and other editors

Add this server to the editor's MCP configuration file (for Cursor: ~/.cursor/mcp.json), then restart it:

{
  "mcpServers": {
    "lws": {
      "url": "https://mcp.lws.net/mcp",
      "headers": { "Authorization": "Bearer VOTRE_JETON" }
    }
  }
}

n8n

1. Add the MCP Client Tool to your AI agent.
2. Endpoint: https://mcp.lws.net/mcp. Transport: HTTP Streamable.
3. Authentication: Bearer Auth, with a token's value.

Choose what the assistant may do

Each token has its own settings:

• the tools it may use, in four levels (see below);
• its lifetime, from 1 to 365 days;
• a maximum number of actions, if you wish;
• purchases: none unless you tick a paid tool, and then within the number of purchases you set;
• the IP addresses and countries it may be used from;
• a note, to remind you what it is for.

Start with read-only access, and create one token per assistant and per use. For the whole account, the Limites (Limits) page also sets the number of actions per hour and per day (refuse beyond, tolerate a margin, or only warn), purchases per day and per month, the allowed IP addresses and countries, and a read-only mode.

Read tools change nothing. Write tools add or protect; sensitive tools can take a site or its e-mail down (DNS zone, name servers) or prepare a transfer. Paid tools draw on your prepaid credit.

Stay in control

• Logs: every action of your assistants (date, token, tool, outcome, IP address, country), kept 90 days, with filters and a CSV, JSON or YAML export.
• E-mail alerts: token created, expiry close, quota nearly used up, limit reached, sign-in refused or from a new network, and every purchase, always reported.
• History: portal sign-ins, changes to tokens and settings, purchases, kept one year.
• At any time, you can suspend, regenerate or revoke a token, and sign your other devices out of the portal.

Good to know

• An assistant can be wrong: read what it suggests before a change to a DNS zone, name servers or a transfer.
• After an error or a timeout, an operation may have been made all the same: the assistant is told to check before trying again, and so should you.
• A purchase made by the assistant is an order like any other, under LWS's general terms of sale: registering and renewing a domain name carry no right of withdrawal.
• What the MCP returns to the assistant (domains, DNS zones…) goes to its publisher, which handles it under its own terms.
• LWS will never ask you for your API key or your tokens. The MCP's terms of use (in French) set out the rules of the service.