Linux Do

Created By
Pleasurecruisea year ago
Overview

what is Linux Do?

Linux Do is a multi-purpose MCP (Microservice Control Panel) server designed to facilitate various API interactions and community engagement.

how to use Linux Do?

To use Linux Do, you need to install it using Node.js or Python, and set up your API key and username in the environment variables. You can then access various API endpoints for topics, notifications, and user interactions.

key features of Linux Do?

  • Access to a variety of API endpoints for community topics and notifications.
  • Support for both Node.js and Python installations.
  • User-specific features like bookmarks and private messages.

use cases of Linux Do?

  1. Engaging with community topics and discussions.
  2. Tracking unread posts and notifications.
  3. Managing user bookmarks and private messages.

FAQ from Linux Do?

  • How do I get my API key?

You can obtain your API key by running the provided script in the installation instructions.

  • Is Linux Do free to use?

Yes! Linux Do is open-source and free to use for everyone.

  • What programming languages are supported?

Linux Do supports both Node.js and Python for installation.

Server Config

{
  "mcpServers": {
    "linux-do": {
      "command": "npx",
      "args": [
        "-y",
        "@pleasure1234/linux-do-mcp"
      ],
      "env": {
        "LINUX_DO_API_KEY": "your-api-key-here",
        "LINUX_DO_USERNAME": "your-username"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Pleasurecruise
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago