Agent Reach
When to Use
Trigger phrases:
"agent reach"
"Scrape Twitter tweets, threads, search results without API keys"
"Read Reddit posts, comments, subreddit feeds"
"Get YouTube video transcripts and metadata"
Scrape Twitter tweets, threads, search results without API keys
Read Reddit posts, comments, subreddit feeds
Get YouTube video transcripts and metadata
Scrape XiaoHongShu (Little Red Book) posts
Monitor Bilibili video content
Search across platforms for competitive intelligence
Gather social proof and sentiment data
Research trending content for viral creation
When NOT to use: When you already have API access (use native tools), when the platform blocks scraping ethically, when data doesn't need real-time freshness
When NOT to Use
- When a simpler HTTP client would suffice
- For internal tools that do not need cross-platform compatibility
- When the tool is used by a single agent in a single context
Overview
Agent Reach implements a Model Context Protocol server for Model Context Protocol.
Architecture
- Server — MCP-compliant server exposing tools and resources
- Transport — stdio or HTTP transport layer
- Tools — Callable functions with JSON Schema definitions
- Resources — Readable data sources with URI-based access
Setup
- Install the MCP server package
- Configure environment variables and credentials
- Register the server in MCP client configuration
- Test tool invocations and resource access
Configuration
- Server name and version
- Transport type (stdio, SSE, HTTP)
- Tool definitions with input/output schemas
- Resource URI patterns
- Authentication and rate limiting
Integration
- Compatible with Claude, Cursor, and other MCP clients
- Supports streaming responses for large payloads
- Handles errors with standard MCP error codes
Anti-Rationalization Table
| Rationalization |
Reality |
| "I will just use curl" |
MCP handles auth, retries, streaming, and type safety. Use the SDK. |
| "One mega-server is simpler" |
Single-responsibility servers are easier to debug and maintain. |
| "MCP is just a wrapper" |
MCP enables cross-platform tool sharing. It is infrastructure, not overhead. |
// Example: MCP server tool definition
import { McpServer } from "@modelcontextprotocol/sdk";
const server = new McpServer({ name: "my-tools", version: "1.0.0" });
server.tool("search", { query: z.string() }, async ({ query }) => {
const results = await search(query);
return { content: [{ type: "text", text: JSON.stringify(results) }] };
});
Process
- Prepare — Gather requirements, verify prerequisites, set up environment
- Execute — Run agent reach workflow with configured parameters
- Verify — Validate output meets requirements, document results
Verification
1---2name: agent-reach3description: Use when universal internet scraper for AI agents. Read and search Twitter,4 Reddit, YouTube, GitHub, Bilibili, XiaoHongShu, LinkedIn, V2EX, RSS, web pages.5 Zero API fees. Use when agents need real-time social media data, content research,6 or trend monitoring.7domain: mcp8author: oyi779license: Apache-2.010subdomain: mcp11tags:12- agent13- ai-agent14- api15- github16- mcp-server17- model-context-protocol18- monitoring19- reach20version: 1.0.021category: mcp22metadata:23 source: https://skillmd.com/skills/oyi77/agent-reach24---2526# Agent Reach2728## When to Use2930**Trigger phrases:**31- "agent reach"32- "Scrape Twitter tweets, threads, search results without API keys"33- "Read Reddit posts, comments, subreddit feeds"34- "Get YouTube video transcripts and metadata"353637- Scrape Twitter tweets, threads, search results without API keys38- Read Reddit posts, comments, subreddit feeds39- Get YouTube video transcripts and metadata40- Scrape XiaoHongShu (Little Red Book) posts41- Monitor Bilibili video content42- Search across platforms for competitive intelligence43- Gather social proof and sentiment data44- Research trending content for viral creation45- **When NOT to use**: When you already have API access (use native tools), when the platform blocks scraping ethically, when data doesn't need real-time freshness464748## When NOT to Use4950- When a simpler HTTP client would suffice51- For internal tools that do not need cross-platform compatibility52- When the tool is used by a single agent in a single context535455## Overview5657Agent Reach implements a Model Context Protocol server for Model Context Protocol.5859## Architecture6061- **Server** — MCP-compliant server exposing tools and resources62- **Transport** — stdio or HTTP transport layer63- **Tools** — Callable functions with JSON Schema definitions64- **Resources** — Readable data sources with URI-based access6566## Setup67681. Install the MCP server package692. Configure environment variables and credentials703. Register the server in MCP client configuration714. Test tool invocations and resource access7273## Configuration7475- Server name and version76- Transport type (stdio, SSE, HTTP)77- Tool definitions with input/output schemas78- Resource URI patterns79- Authentication and rate limiting8081## Integration8283- Compatible with Claude, Cursor, and other MCP clients84- Supports streaming responses for large payloads85- Handles errors with standard MCP error codes8687## Anti-Rationalization Table8889| Rationalization | Reality |90|---|---|91| "I will just use curl" | MCP handles auth, retries, streaming, and type safety. Use the SDK. |92| "One mega-server is simpler" | Single-responsibility servers are easier to debug and maintain. |93| "MCP is just a wrapper" | MCP enables cross-platform tool sharing. It is infrastructure, not overhead. |9495```typescript96// Example: MCP server tool definition97import { McpServer } from "@modelcontextprotocol/sdk";9899const server = new McpServer({ name: "my-tools", version: "1.0.0" });100101server.tool("search", { query: z.string() }, async ({ query }) => {102 const results = await search(query);103 return { content: [{ type: "text", text: JSON.stringify(results) }] };104});105```106107108## Process1091101. **Prepare** — Gather requirements, verify prerequisites, set up environment1111. **Execute** — Run agent reach workflow with configured parameters1121. **Verify** — Validate output meets requirements, document results113114## Verification115116- [ ] All steps executed successfully117- [ ] Results validated against acceptance criteria118- [ ] Error handling tested with edge cases119- [ ] Documentation updated with findings