原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Xtracticle

作者:ahmetdeveci3112-crypto版本 3.2.0i★ –i在云端运行
注册名称com.xtracticle/xtracticle

安装

概览

作者提供的说明(英文原文)

Read public X (Twitter) posts, threads and X Articles as clean Markdown. Read-only, no auth.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在云端运行
  • 传输方式: Streamable HTTP
  • 分类: 营销与社交媒体

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://xtracticle.com/mcp

在终端中运行这条命令

claude mcp add --transport http xtracticle https://xtracticle.com/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "xtracticle": {
      "url": "https://xtracticle.com/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "xtracticle": {
      "type": "http",
      "url": "https://xtracticle.com/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://xtracticle.com/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 xtracticle.com 验证(注册中心会核实域名所有权)

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

与“营销与社交媒体”中的其他服务器比较i

  • 星标数多于此分类中其他 2956 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 2956 个服务器的 46% 更新
  • 基础检查结果等于或优于此分类中其他 2956 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Xtracticle 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(3.2.0)于34天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

MCP YouTube Transcript

作者:jkawamoto

An MCP server retrieving transcripts of YouTube videos

在你的电脑上运行★ 495MIT9天前更新
安装

Google Analytics MCP

作者:surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

在你的电脑上运行★ 244MIT9天前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Xtracticle Download X (Twitter) Articles, threads & posts as PDF, Markdown, EPUB/Kindle, text or a ZIP with images. Free, open source, no login required.

Features • Getting Started • Architecture • SEO & AI • API • Contributing


Live: xtracticle.com — or just change x.com to xtracticle.com in any post URL.

Features

Export formats
FormatWhat you get
PDFA4, print-ready; title/author/date/source header, images, page numbers, clickable source link. Rendered page by page so long articles never produce blank PDFs and lines are never cut.
MarkdownHeadings, bold/italic/strikethrough, links, nested lists, quotes, code, dividers, images, video thumbnails. Optional YAML front-matter (Obsidian properties, Hugo/Jekyll/Astro).
EPUB 3Reflowable e-book with embedded images and metadata — Kindle (Send to Kindle), Kobo, Apple Books.
ZIP + imagesMarkdown + every image stored locally — an offline archive that survives deleted posts.
TextClean .txt.
ObsidianCopies the Markdown and opens a new note via obsidian://new.
Content
  • 📝 X Articles — full Draft.js conversion: cover, inline images, videos, captions, embedded posts
  • 🧵 Threads from any post — paste the first, a middle or the last post; the whole self-thread is assembled (other people's replies are excluded)
  • 💬 Posts — line breaks, photos, videos and quoted posts
  • 🔗 Flexible input — x.com, twitter.com, mobile, fxtwitter/vxtwitter/fixupx, nitter/xcancel links, /i/web/status/, bare IDs, links inside shared text
Workflow
  • 🔁 URL swap — xtracticle.com/{user}/status/{id} opens a post directly, with rich link previews (Open Graph) when shared
  • 📚 Batch mode — up to 20 links → one ZIP of Markdown files
  • 🔖 Bookmarklet and PWA share target (share from the X app on Android)
  • 🔊 Listen — read aloud with the browser's text-to-speech
  • 📱 iPhone/iPad Shortcut — share a post from the X app straight to Xtracticle (public/shortcuts/)
  • 🤖 MCP server + Markdown API — AI assistants read X posts as Markdown (/mcp, /api/markdown/:id)
  • 📜 History, 🌙 dark mode, 🌍 English, Español, Português, 日本語, 简体中文, العربية, Türkçe (Arabic is right-to-left)
  • 📈 Analytics events — extract, download (format), copy, share, listen, batch_extract, errors — in GA4

Getting Started

git clone https://github.com/ahmetdeveci3112-crypto/Xtracticle.git

cd Xtracticle npm install npm run dev

The dev server runs at http://localhost:5173. /api/* is served by the same handler as the Worker (src/shared/api.ts), and every landing page is rendered on the fly — no wrangler needed.

ScriptDescription
npm run devVite dev server with the API
npm run buildProduction build → dist/ (all landing pages, 404, sitemap)
npm run preview:workerBuild and run the real Worker locally with wrangler dev (SSR status pages, 404s, _headers)
npm run lintType-check the app and the Worker

Deployment

Cloudflare Workers + Static Assets, deployed automatically on push to main (build: npm run build, deploy: npx wrangler deploy). No environment variables.

wrangler.json:

  • run_worker_first — only /api/*, /mcp, /video/* and /*/status/* hit the Worker; everything else is served straight from the CDN
  • not_found_handling: "404-page" — unknown URLs return a real 404 (no soft-404s)
  • public/_headers — security headers, Link: , download headers for the iOS Shortcut

Architecture

Browser ──► Cloudflare

├─ Static assets (dist/) /, /x-article-to-pdf, /tr/, … , 404.html, sitemap.xml └─ Worker (src/worker.ts) ├─ /api/thread/:id, /api/tweet/:id ──► src/shared/api.ts ──► FxTwitter API │ (edge cache, 5 min) └─ /{user}/status/{id} ──► app shell + per-post OG tags + preloaded JSON (noindex)

src/ ├── App.tsx UI: extraction, exports, batch mode, deep links ├── i18n.ts UI strings (en, tr, es, pt, ja, zh) ├── lib/export.ts PDF (jsPDF + html2canvas-pro), EPUB, ZIP (fflate), Obsidian ├── lib/url.ts Input + path parsing ├── lib/analytics.ts GA4 event helper ├── shared/fx.ts FxTwitter client (v2 thread endpoint + v1 fallback), shared by Worker & dev server ├── shared/api.ts JSON API handler with edge caching ├── shared/convert.ts Posts / threads / Draft.js articles → Markdown + text + metadata (app + Worker) ├── shared/markdown.ts GET /api/markdown/:id ├── shared/mcp.ts Remote MCP server (POST /mcp) ├── shared/text.ts Title extraction └── worker.ts Cloudflare Worker (API + status-page SSR) site/ ├── blocks.ts Types + localized shared blocks (shortcuts, privacy) ├── pages.ts English pages (one per search intent) + page registry ├── pages-{es,pt,ja,zh,ar,tr}.ts The same pages, localized (linked by group) ├── curated.ts Weekly “Best X Articles” pages from site/curated/*.json ├── guides.ts /guides — informational guides ├── mcp-page.ts /mcp-server — MCP setup docs ├── render.ts Head/meta/JSON-LD/content/footer rendering └── plugin.ts Vite plugin: emits every page, 404.html and sitemap.xml

Heavy export libraries are dynamically imported, so the initial page only loads React + the app.

SEO & AI Discoverability

LayerImplementation
Intent pages/x-article-to-pdf, /x-article-to-markdown, /x-thread-to-pdf, /x-article-to-epub, /save-x-articles-to-obsidian, /thread-reader-app-alternative — each with unique, visible HTML content and FAQ
LanguagesEvery page in 7 languages (/, /es/…, /pt/…, /ja/…, /zh/…, /ar/…, /tr/…) + UI in 7 languages; first-visit language banner, remembered choice redirects (never for crawlers)
Crawlable contentContent is static HTML outside the React root — no JS needed to index it
Structured dataWebApplication, FAQPage (matches visible FAQ), BreadcrumbList
i18nReciprocal hreflang for every translation group + x-default
Share pages/{user}/status/{id} get post-specific OG/Twitter tags; noindex, follow
Sitemap / 404Generated at build; real 404 status for unknown URLs
AI/llms.txt, /llms-full.txt, AI crawlers allowed in robots.txt

API

GET /api/thread/:id  → { tweets: Tweet[], count, isThread }   # self-thread containing :id

GET /api/tweet/:id → Tweet GET /api/markdown/:id → text/markdown # ?format=markdown|text&thread=0|1&front_matter=0|1 POST /mcp → MCP (Streamable HTTP, stateless), tool read_x_post

Tweet mirrors the FxTwitter status object (text, author, media, quote, article, …). Responses are edge-cached for 5 minutes — please be gentle.

Weekly “Best X Articles”

/best-x-articles is a hand-reviewed weekly selection built from site/curated/*.json (title, author and a one-sentence summary in our own words — never the article text).

npm run curate -- 2026-W41 https://x.com/user/status/123 https://x.com/other/status/456

→ site/curated/2026-w41.json with title/author/lang filled in; write "intro", "topic" and "summary"

npm run build # issues with an empty summary are skipped automatically

The newest issue is shown on /best-x-articles (its /best-x-articles/ page canonicals to the hub until the next issue); older issues stay at /best-x-articles/ .

Contributing

  1. Fork the repo
  2. Create a feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes
  4. Open a Pull Request

Notes:

  • Landing page copy lives in site/pages.ts; run npm run build to see the generated HTML
  • Keep src/shared/* free of DOM/Node-only APIs — it runs in both the Worker and the dev server
  • Test Worker-only behavior (SSR, 404, headers) with npm run preview:worker

License

MIT

问 PopNx