Add X Twitter Scraper to MCP Servers

[kriptoburak]

Adds X Twitter Scraper to the MCP Servers table.

• GitHub: https://github.com/Xquik-dev/x-twitter-scraper
• Docs: https://docs.xquik.com

[qodo-code-review]

Review Summary by Qodo

Add x-twitter-scraper MCP server to documentation

✨ Enhancement

Walkthroughs

Description

• Adds x-twitter-scraper to MCP Servers list
• Includes link to GitHub repository and feature description
• Highlights 40+ tools, REST API, and webhook support

Diagram

flowchart LR
  README["README.md"] -- "adds x-twitter-scraper entry" --> MCPServers["MCP Servers Section"]
  MCPServers -- "includes" --> Features["40+ tools, REST API, webhooks"]

Loading

File Changes

1. README.md 📝 Documentation +1/-0

Add x-twitter-scraper MCP server entry

• Adds new entry for x-twitter-scraper in MCP Servers section
• Includes GitHub repository link and feature description
• Describes X (Twitter) data extraction capabilities for AI agents

README.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX Issues (0)

1. Non-title entry label ☑ 🐞 ≡

Description

The new MCP Servers entry uses the repository slug "x-twitter-scraper" as the link text instead of a
human-readable Title, making it inconsistent with the rest of the MCP Servers section and the
documented "[Title](link) - Description." format. This reduces scanability and violates the repo’s
stated contribution format expectations.

Code

README.md[28]

+- [x-twitter-scraper](https://github.com/Xquik-dev/x-twitter-scraper) - X (Twitter) data extraction & automation skill for AI coding agents with 40+ tools, REST API, MCP server, and HMAC webhooks.

Evidence

The contribution guide explicitly specifies the list item format uses a "Title" and existing MCP
Server entries follow that pattern (e.g., "Atlassian Remote MCP Server", "GitHub MCP Server"), while
the new entry uses a lowercase repo slug as its label.

contributing.md[5-10]
README.md[22-28]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The MCP Servers list entry uses a repo slug (lowercase, hyphenated) as the link label instead of a human-readable title, which diverges from the repo’s documented `[Title](link) - Description.` format and the established style of the MCP Servers section.
### Issue Context
This is a documentation consistency/readability issue in `README.md`.
### Fix Focus Areas
- README.md[28-28]
### Suggested change
Update the link text to a title-cased, human-readable name (keep the URL unchanged) and keep the description ending with a period.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Overlong list description ☑ 🐞 ≡

Description

The added MCP server description is materially longer than the other MCP Servers entries,
conflicting with the guideline to keep descriptions short and simple. This makes the section harder
to scan compared to peer entries with notably shorter descriptions.

Code

README.md[28]

+- [x-twitter-scraper](https://github.com/Xquik-dev/x-twitter-scraper) - X (Twitter) data extraction & automation skill for AI coding agents with 40+ tools, REST API, MCP server, and HMAC webhooks.

Evidence

The contribution guide instructs that descriptions should be short and simple; existing MCP Server
descriptions are typically ~8–13 words, while the new entry’s description is ~21 words and
enumerates multiple features in one sentence.

contributing.md[7-10]
README.md[23-28]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The new MCP Servers entry description is much longer than neighboring entries, conflicting with the guideline to keep descriptions short and simple and reducing scannability.
### Issue Context
This is a documentation consistency issue in `README.md` within the MCP Servers list.
### Fix Focus Areas
- README.md[28-28]
### Suggested change
Condense the description to a single concise clause (still ending with a period), e.g. "X (Twitter) data extraction and automation MCP server for Claude-compatible agents."

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more