mcp-server-admintasks

Created By
mge1512a year ago
MCP Server implementing various tools to execute admin tasks on a Linux system.
Overview

what is mcp-server-admintasks?

MCP Server Admintasks is a project that implements various tools to execute administrative tasks on a Linux system, aimed at simplifying server management.

how to use mcp-server-admintasks?

To use this project, you can build the RPM packages for your Linux distribution from the provided repository and follow the usage instructions with the mcphost tool.

key features of mcp-server-admintasks?

  • Implements various tools for Linux server administration.
  • Provides RPM packages for multiple Linux distributions.
  • Designed for ease of use in executing admin tasks.

use cases of mcp-server-admintasks?

  1. Automating routine server maintenance tasks.
  2. Managing user accounts and permissions on Linux servers.
  3. Monitoring system performance and resource usage.

FAQ from mcp-server-admintasks?

  • Is this project ready for production use?

No, this project is heavily under development and not yet ready for production use.

  • What license is mcp-server-admintasks under?

The project is licensed under the MIT license.

  • Where can I find the RPM packages?

RPM packages for multiple Linux distributions can be found at the provided OpenSUSE build link.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mge1512
Star
1
Language
Go
License
MIT license
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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