lolzteam-mcp

<h1 align="center">LOLZTEAM MCP</h1> <p align="center"> An MCP server that lets AI assistants search and read the LOLZTEAM Forum and LZT Market through their official APIs. </p> <p align="center"> <a href="https://www.npmjs.com/package/lolzteam-mcp"><img src="https://img.shields.io/npm/v/lolzteam-mcp?label=npm&color=4c9dff" alt="npm"></a> <a href="https://github.com/liwidale/lolzteam-mcp/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/liwidale/lolzteam-mcp/ci.yml?label=tests" alt="Tests"></a> <img src="https://img.shields.io/badge/platform-Node.js%2022%2B-lightgrey" alt="Node.js 22 or newer"> <a href="LICENSE"><img src="https://img.shields.io/github/license/liwidale/lolzteam-mcp?color=3ad37e" alt="MIT License"></a> </p> <p align="center">English · <a href="README.ru.md">Русский</a></p>

An AI assistant cannot read LOLZTEAM or LZT Market on its own: the content sits behind authenticated APIs with their own parameters, pagination and rate limits. LOLZTEAM MCP wraps the official Forum and Market APIs in 24 read-only tools that any client supporting the Model Context Protocol can call. The assistant can search threads and posts, follow a discussion page by page, look up users, search Market listings with category filters, open a listing and check its seller. Results come back as compact JSON with links to the original pages. The endpoint catalog is generated from the official OpenAPI documents, so new API methods and parameters become available without new code.

Contents

• Installation
• What you get
• Getting started
• Usage
• Configuration
• Security
• Troubleshooting
• Development
• How it works
• Project structure
• Contributing
• License

Installation

Installation takes three steps: install Node.js, get an API token and run one setup command. The setup command checks the token and adds the server to your AI clients.

1. Install Node.js

LOLZTEAM MCP runs on Node.js 22.18 or newer. Check the version you have:

node --version

If the command is not found or prints a version below v22.18.0:

• Windows and macOS. Download the LTS installer from nodejs.org and run it.
• Linux. Install Node.js 22 or 24 from your distribution's packages or with a version manager such as nvm.

Open a new terminal window after installing, so the node and npx commands are found.

2. Get an API token

1. Sign in to LOLZTEAM and create an API client at lolz.live/account/api/client-add.
2. Get an access token at lolz.live/account/api/get-token and select these scopes:

| Scope | Needed for | | -------- | ------------------------------------------------------------------------------------------------------------------------------------- | | read | All forum reading tools. | | basic | forum_get_user. | | post | forum_search. The official API documents its search endpoints as requiring this scope. The server uses it only for search requests. | | market | All market_* tools. |

Market API access also requires 200 sympathies on the forum or a paid Market API subscription. Without it the Market tools return a forbidden error, while the forum tools keep working.

Keep the token private. Anyone who has it can use the API on behalf of your account.

3. Run the setup

npx -y lolzteam-mcp setup

The command downloads the latest version and then:

1. Asks for the token. The input stays hidden.
2. Checks the token against both APIs and shows the account it belongs to. A rejected token stops the setup before anything changes.
3. Finds the installed MCP clients: Claude Desktop, Cursor, Windsurf and Antigravity.
4. Asks which of them to configure. Press Enter to configure all of them.
5. Adds the lolzteam server to each configuration file. Other servers and settings stay as they are, and the previous file is saved next to it with a .bak extension.
6. Prints the command for Claude Code.

A typical run looks like this:

LOLZTEAM MCP 1.0.0 setup
Create an API client at https://lolz.live/account/api/client-add, then get a token at https://lolz.live/account/api/get-token with the read, basic, post and market scopes.
API token (input is hidden):
Checking the token...
Forum API: signed in as your_name.
Market API: available.
Found these MCP clients:
  1. Claude Desktop (C:\Users\you\AppData\Roaming\Claude\claude_desktop_config.json)
  2. Cursor (C:\Users\you\.cursor\mcp.json)
Clients to configure, as numbers separated by commas. Press Enter for all:
Claude Desktop: added the lolzteam server to C:\Users\you\AppData\Roaming\Claude\claude_desktop_config.json
Cursor: added the lolzteam server to C:\Users\you\.cursor\mcp.json

Claude Code: run this command with your token in place of <token>:
  claude mcp add --transport stdio --scope user --env LOLZTEAM_TOKEN=<token> lolzteam -- cmd /c npx -y lolzteam-mcp@latest

Restart the configured clients. The lolzteam server and its tools appear after the restart.

Restart the configured clients. The 24 tools appear under the lolzteam server.

The setup speaks the language of your system. Run it with LOLZTEAM_LOCALE=en or LOLZTEAM_LOCALE=ru to choose. The chosen language is also saved for the server.

Setup options

| Option | Effect | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | --yes | Configures every detected client without asking. | | --client <id> | Configures only this client: claude-desktop, cursor, windsurf or antigravity. Repeat it for several clients. Use it when a client has never been started and its folder does not exist yet. | | LOLZTEAM_TOKEN | Environment variable with the token. The setup uses it instead of asking, which lets it run in scripts. |

For example, to configure only Cursor without questions on macOS or Linux:

LOLZTEAM_TOKEN=your-token npx -y lolzteam-mcp setup --yes --client cursor

<details> <summary><b>Set up a client by hand</b></summary> <br>

Use this when the setup command fails, when your client is not in its list or when you prefer to edit the configuration yourself. Any MCP client that starts servers over stdio works.

1. Check that the package runs. The command prints the version:

   npx -y lolzteam-mcp@latest --version
   

2. Quit the client and open its configuration file in a text editor. Create the file if it does not exist yet.

   | Client | Windows | macOS | Linux | | -------------- | ------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------- | | Claude Desktop | %APPDATA%\Claude\claude_desktop_config.json | ~/Library/Application Support/Claude/claude_desktop_config.json | ~/.config/Claude/claude_desktop_config.json | | Cursor | %USERPROFILE%\.cursor\mcp.json | ~/.cursor/mcp.json | ~/.cursor/mcp.json | | Windsurf | %USERPROFILE%\.codeium\windsurf\mcp_config.json | ~/.codeium/windsurf/mcp_config.json | ~/.codeium/windsurf/mcp_config.json | | Antigravity | %USERPROFILE%\.gemini\config\mcp_config.json | ~/.gemini/config/mcp_config.json | ~/.gemini/config/mcp_config.json |

   Other clients describe the location in their documentation. Look for the mcpServers setting.

3. Add the lolzteam server and put your token in place of your-token.

   macOS and Linux:

   {
     "mcpServers": {
       "lolzteam": {
         "command": "npx",
         "args": ["-y", "lolzteam-mcp@latest"],
         "env": {
           "LOLZTEAM_TOKEN": "your-token"
         }
       }
     }
   }
   

   Windows:

   {
     "mcpServers": {
       "lolzteam": {
         "command": "cmd",
         "args": ["/c", "npx", "-y", "lolzteam-mcp@latest"],
         "env": {
           "LOLZTEAM_TOKEN": "your-token"
         }
       }
     }
   }
   

   If the file already has an mcpServers object, add only the "lolzteam": { ... } block inside it and separate it from the other servers with a comma.

4. Save the file and start the client. Claude Desktop keeps running in the tray or menu bar after you close its window, so quit it from there before starting it again.

When npx does not work. Install the package once and point the client straight to it:

npm install -g lolzteam-mcp

npm root -g

The second command prints the folder with global packages. In the configuration, use node as the command and the full path to lolzteam-mcp/dist/index.js inside that folder as the argument. On Windows, double every backslash in JSON:

"lolzteam": {
  "command": "node",
  "args": ["C:\\Users\\you\\AppData\\Roaming\\npm\\node_modules\\lolzteam-mcp\\dist\\index.js"],
  "env": {
    "LOLZTEAM_TOKEN": "your-token"
  }
}

This copy does not update itself. Run npm install -g lolzteam-mcp@latest to get a new version.

</details>

Claude Code

Claude Code keeps its own list of servers. Add the server with one command and put your token in place of your-token.

macOS and Linux:

claude mcp add --transport stdio --scope user --env LOLZTEAM_TOKEN=your-token lolzteam -- npx -y lolzteam-mcp@latest

Windows:

claude mcp add --transport stdio --scope user --env LOLZTEAM_TOKEN=your-token lolzteam -- cmd /c npx -y lolzteam-mcp@latest

Run claude mcp list to check that lolzteam is connected.

Updating

The configuration runs npx -y lolzteam-mcp@latest, so npm fetches the newest published version when a client starts the server. Restart the client to pick up a new release. Run the setup again only to change the token or add another client.

Install from source

Use this to run your own changes or a version that is not published yet. You need Git in addition to Node.js.

git clone https://github.com/liwidale/lolzteam-mcp.git
cd lolzteam-mcp
npm ci
npm run build
node dist/index.js setup

When the setup runs from a cloned folder, it writes the full path to node and to dist/index.js into the client configuration instead of npx. Pull new commits and run npm ci and npm run build to update.

Uninstalling

1. Remove the lolzteam entry from each client configuration file, or restore the