Tldr Pages

io.github.pipeworx-iov0.1.2更新於 Sep 30, 2026

tldr-pages MCP — fetched from the canonical github repo.

已驗證Streamable HTTP可網頁執行Developer ToolsKnowledge & Memory

概覽

AI 產生的概覽

讓助理依指令、平台與語言查詢社群維護的 tldr 命令列速查頁。

功能
提供 tldr-pages 專案的內容，也就是命令列工具的簡化手冊頁。工具包含 page（渲染某個指令的速查頁）、commands（列出某個平台可用的指令）、platforms（列出支援的平台）以及 search（依標題子字串搜尋）。頁面快取 24 小時，取自 tldr-pages 官方儲存庫。
適用情境
當助理需要 Linux、macOS、Windows、Android、SunOS 或 FreeBSD 上 shell 指令的簡明範例用法，或需要列出、搜尋可用指令時適用。它只是參考資料查詢，不是系統管理工具。
執行需求
遠端 streamable HTTP 端點位於 gateway.pipeworx.io；宣告中首次呼叫不需帳號或 API 金鑰。另提供本機 stdio 版本，透過 npx 執行 npm 套件，需要 Node.js。存取閘道或上游 tldr-pages 資料來源需要網路。
安裝前請注意
閘道端點還會暴露 Pipeworx 共用中繼工具，例如 ask_pipeworx、discover_tools、search_within 以及 remember/recall，因此列出的工具數量多於本套件自身的工具，會佔用額外上下文。這些中繼工具可將問題路由到整個閘道目錄。本機 stdio 套件只暴露本套件的工具。不要求任何憑證。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Tldr Pages，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "tldr-pages": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/tldr-pages/mcp"
    }
  }
}

README

@pipeworx/tldr-pages

tldr-pages MCP — community maintained simplified man pages. Keyless. Cached 24h in-pack.

Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.

Tools

  • page(command, platform?, language?) — render tldr page for a command
  • commands(platform?, language?) — list commands available for a platform
  • platforms() — list supported platforms
  • search(query, platform?, language?, limit?) — substring search across page titles

platform: common (default) | linux | osx | windows | android | sunos | freebsd. language: ISO 639-1, default en.

Data source

https://raw.githubusercontent.com/tldr-pages/tldr/main/pages...

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

json
{  "mcpServers": {    "tldr-pages": {      "url": "https://gateway.pipeworx.io/tldr-pages/mcp"    }  }}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/tldr-pages/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

json
{  "mcpServers": {    "pipeworx": {      "url": "https://gateway.pipeworx.io/mcp"    }  }}

Both URLs reach the same gateway and the same 1684+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

bash
curl -X POST https://gateway.pipeworx.io/v1/tools/page \  -H 'Content-Type: application/json' \  -d '{"command":"ls"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/page. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

json
{  "mcpServers": {    "tldr-pages": {      "command": "npx",      "args": ["-y", "@pipeworx/mcp-tldr-pages"]    }  }}

Or run it directly to confirm it starts:

bash
npx -y @pipeworx/mcp-tldr-pages

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Tldr Pages data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

來源：README.md，提交 b00c46a

工具

0
工具後設資料尚未被收錄。

版本歷史

3
  1. v0.1.2最新Sep 27, 2026
  2. v0.1.1Sep 25, 2026
  3. v0.1.0Sep 16, 2026