get_webpage_markdownLABSCO SUMMARY
Five formats stop needing five different workarounds.
A link is a link — page, video, thread, PDF or doc — and each one has a tool that returns readable text, so research does not stall at whichever format the source happens to be in.
What it is
A reader for five kinds of internet content, each with its own tool. You pass a URL; what comes back is the content as text or Markdown rather than the page around it.
What you get
- A webpage fetched through Jina reader and returned as Markdown
- The transcript of a YouTube video, from its ID or URL
- A tweet thread pulled back as a thread, not as a single post
- The text of a PDF at a URL
- A public Google Doc returned as Markdown
Requirements
npx on your PATH — the published package runs without cloning anything. Every source is fetched live at request time, and the Google Doc tool only reaches documents that are publicly shared.
Setup effort
One command — npx -y @x-mcp/ireader@latest
USE CASES
01
Reading an article without the page around it
Fetch the URL and get Markdown back — headings and body text, without the navigation, the cookie banner and the newsletter interruption.
02
Getting the content of a talk without watching it
Pull the video's transcript from its URL and read, search or summarize it in a fraction of the running time.
03
Capturing an argument that was made across a thread
Fetch the whole thread rather than the one post that was linked, so the point that only makes sense in sequence survives.
04
Reading a paper that is behind a PDF link
Extract the text straight from the URL, so a document that would otherwise need downloading and opening becomes something to quote from.
05
Working from a shared document
Pull a publicly shared Google Doc back as Markdown, which is how a specification or a brief gets into the conversation without copy-and-paste.
5 tools
Listed in project docs. Your client may show a different list.
get_youtube_transcriptget_tweet_threadget_pdfget_public_google_doc_markdownBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @x-mcp/ireader@latestMCP Clients
Claude Desktop, Any MCP client
JSON
{
"mcpServers": {
"ireader": {
"command": "npx",
"args": [
"-y",
"@x-mcp/ireader@latest"
]
}
}
}
