Tldr Pages

io.github.pipeworx-iov0.1.2Updated Sep 30, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsKnowledge & Memory

Overview

AI-generated overview

Lets an assistant look up community-maintained tldr command-line cheat sheets by command, platform, and language.

What it does
Serves the tldr-pages project, a set of simplified man pages for command-line tools. Tools include page to render a cheat sheet for a command, commands to list commands for a platform, platforms to list supported platforms, and search for substring matches across page titles. Pages are cached for 24 hours and fetched from the canonical tldr-pages repository.
When to use it
Useful when an assistant needs quick, example-driven usage notes for shell commands on Linux, macOS, Windows, Android, SunOS, or FreeBSD, or when it should list or search available commands. It is a reference lookup, not a system administration tool.
Requirements
A remote streamable HTTP endpoint at gateway.pipeworx.io; no account or API key is declared for the first calls. A local stdio variant is also offered as an npm package run through npx, which needs Node.js. Network access is required to reach the gateway or the upstream tldr-pages source.
Before you install
The gateway endpoint also exposes shared Pipeworx meta-tools such as ask_pipeworx, discover_tools, search_within, and remember/recall, so the listed tool count is larger than this pack's own tools and consumes extra context. The meta-tools can route questions across the whole gateway catalog. The local stdio package exposes only this pack's tools. No credentials are requested.

Installation

In SourceWeft

  1. Open Tldr Pages in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "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

Source: README.md at commit b00c46a

Tools

0
Tool metadata has not been indexed yet.

Version history

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