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