Unix Manual Server (MCP)

Created By
tizeea year ago
An MCP server that provides Unix command documentation directly within LLMs conversations.
Overview

What is Unix Manual Server (MCP)?

Unix Manual Server (MCP) is a server that provides Unix command documentation directly within conversations with LLMs, such as Claude.

How to use Unix Manual Server (MCP)?

To use the server, install it in a compatible client like Claude Desktop, and then you can request command documentation, list common commands, or check if a command exists.

Key features of Unix Manual Server (MCP)?

  • Retrieve help pages, man pages, and usage information for Unix commands.
  • Discover available commands on your system, categorized by function.
  • Verify if a specific command is available and get its version information.

Use cases of Unix Manual Server (MCP)?

  1. Getting help with specific Unix commands during development.
  2. Listing all available Unix commands for quick reference.
  3. Checking the availability of commands on a system before executing them.

FAQ from Unix Manual Server (MCP)?

  • Can I use Unix Manual Server with any LLM?

Currently, it is designed for use with Claude and other MCP-compatible clients.

  • Is there a cost to use Unix Manual Server?

No, it is free to use under the MIT license.

  • How does the server ensure security?

The server validates command names, executes commands without using a shell, and sets timeouts to prevent command injection.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tizee
Star
0
Language
Python
License
MIT 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