linux-do

This MCP server wraps the Linux Do Discourse API access into a reusable MCP endpoint. It exposes a suite of tools that map to the Linux Do forum features, including topics with new posts, most active topics, recently popular topics, latest classified topics, and various authenticated capabilities like unread topics, unseen topics, posted topics, notifications, and search. Each tool corresponds to a specific API endpoint on linux.do, enabling automation, monitoring, and integration with your own dashboards or bots. Use the configured MCP entry (linux-do-mcp) to start the server, then invoke the tools via the standard MCP interface to fetch data, parse results, and drive workflows (e.g., alerting on new posts, tracking unread topics, or aggregating popular discussions).

Prerequisites:

• Node.js and npm installed on your system (or access to an environment that can run npx).
• Optional: an API key for Linux DO to enable authenticated endpoints.

Node.js/MCP installation:

1. Ensure you have an API key from Linux DO and a username if you plan to access authenticated endpoints.
2. Install and run the MCP server using the example configuration provided below.

Code examples:

{
  "mcpServers": {
    "linux-do-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pleasure1234/linux-do-mcp"
      ],
      "env": {
        "LINUX_DO_API_KEY": "your-api-key-here",
        "LINUX_DO_USERNAME": "your-username"
      }
    }
  }
}

Python (uvx) installation example (alternative):

{
  "mcpServers": {
    "linux-do-mcp": {
      "command": "uvx",
      "args": [
        "linux-do-mcp"
      ],
      "env": {
        "LINUX_DO_API_KEY": "your-api-key-here",
        "LINUX_DO_USERNAME": "your-username"
      }
    }
  }
}

Run commands:

• For Node (npx): start with the provided mcp.json and run the MCP runner in your environment.
• For Python (uvx): ensure uv is installed and use the uvx runner with the same configuration.

Note: Replace placeholder API key and username with your actual credentials if you intend to access authenticated endpoints.

Tips:

• The Linux Do MCP server exposes both public endpoints (e.g., latest.json, top.json, hot.json) and authenticated endpoints (e.g., unread.json, unseen.json, notifications.json). Ensure you supply LINUX_DO_API_KEY and LINUX_DO_USERNAME when you need authenticated access.
• If you run into API rate limits or connectivity issues, verify network access to https://linux.do and confirm that the API key is valid.
• The npm package name for this MCP server appears to be @pleasure1234/linux-do-mcp; use the same package name when installing in environments that rely on npm/pnpm.
• When upgrading the MCP server, review the Tools List in the repository to understand any new endpoints or changes to the API surface.
• For authenticated features that reference user-specific endpoints (bookmarks, private messages), you must provide a valid LINUX_DO_USERNAME and a corresponding API_KEY.