local-manpage-mcp-server

Created By
domesticodea year ago
A MCP server which loads the man pages of tools in $PATH as resource. The goal is to provide the LLM with context of the commands on the host machine
Overview

what is local-manpage-mcp-server?

local-manpage-mcp-server is an MCP server that extracts and exposes the man pages of all executables in your $PATH as MCP resources, providing LLMs with direct access to up-to-date documentation for commands installed on the host system.

how to use local-manpage-mcp-server?

To use the server, clone the repository, set up a Python virtual environment, install the required packages, and run the server. You must also execute the create_all_manpage_files tool to generate the MCP resources based on your system's commands.

key features of local-manpage-mcp-server?

  • Extracts and serves man pages as MCP resources.
  • Provides a self-explanatory server for LLMs to describe workflows automatically.
  • Supports Linux distributions exclusively.

use cases of local-manpage-mcp-server?

  1. Enabling LLMs to access command documentation dynamically.
  2. Assisting developers in understanding command usage without leaving their development environment.
  3. Automating command explanations in applications.

FAQ from local-manpage-mcp-server?

  • Is this server compatible with macOS or Windows?

No, it is designed exclusively for Linux distributions.

  • What permissions are required to run this server?

You need read access to all directories in your $PATH and write permissions for a local manpages folder.

  • Can I generate man pages for a large number of binaries?

Yes, but be aware that it can be CPU- and disk-intensive.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
domesticode
Star
1
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