liwidale/lolzteam-mcp

An MCP server that lets AI assistants search and read the LOLZTEAM Forum and LZT Market through their official APIs.
English · Русский
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:
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
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:
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 | 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:
Set up a client by hand
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:
2. Quit the client and open its configuration file in a text editor. Create the file if it does not exist yet.