← Back to directory
A

Agent Reach

Community
Give AI agents access to content across the internet.
GitHub source repository ↗
★ 60.2k Stars Category · Other Very popular
46FMRS · D
Reliability
4/20
Security and permissions
8/20
Maintenance
12/20
Documentation
13/20
Setup experience
9/20

The source presents Agent Reach primarily as a CLI-based multi-platform capability orchestration layer, not as a standalone MCP server with a published tool list and transport configuration. It suits users who want command-line agents to read and search internet content across many platforms; login-based platforms require careful account and credential risk assessment.

Read the FMRS scoring method →

Agent Reach is an open-source capability layer and CLI that selects, installs, checks, and routes upstream tools for web pages, YouTube, RSS, GitHub, Twitter/X, Bilibili, Reddit, Xiaohongshu, and other platforms. It is not an independent content-reading service: agents directly call the upstream tools for reading and search. The project requires Python 3.10+ and is licensed under MIT.

Tools

The tool list has not been reviewed yet.

Setup

Give a command-capable agent the instruction “Install Agent Reach: https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/install.md”. Installation can use agent-reach install --env=auto; --safe enables safe mode and --dry-run previews operations. Run agent-reach doctor afterward to check channel status. OpenClaw users must enable exec permissions and restart the Gateway first.

Fit and risk

Best for

  • Users who need Claude Code, OpenClaw, Cursor, or Windsurf to access content across multiple platforms
  • Individuals and developers seeking free or open-source upstream tools for web research
  • Agent workflows that need centralized installation, diagnostics, and backend routing

Not for

  • Tasks requiring graphical browser interaction, form submission, or automated login
  • Deployments requiring a standalone MCP server or a documented MCP transport
  • Environments that do not allow shell command execution by the agent
  • Use cases requiring every platform to work without login state or cookies

Required permissions

  • The agent must execute shell commands, including pip install, system dependency installation, and upstream CLI calls
  • Some channels require local browser login state, cookies, or tokens
  • Credentials are stored locally in ~/.agent-reach/config.yaml; the README states the file mode is 600

Risks and side effects

  • Cookie- or login-state-based access to Twitter/X, Xiaohongshu, Reddit, and similar platforms may trigger detection, restrictions, or account bans
  • The default installation may install Node.js, gh CLI, mcporter, and other system infrastructure, and modify agent skills and MCP configuration
  • Platform anti-crawling changes or upstream tool changes may break individual channels
  • Server deployments may require a proxy; the README estimates roughly $1 per month

Troubleshooting

  1. Run agent-reach doctor to inspect channel status, active backends, and repair advice
  2. OpenClaw users should verify tools.profile is coding and restart the Gateway
  3. Configure the required login state or cookies for platforms that need authentication
  4. Use agent-reach install --safe or --dry-run to inspect installation impact
  5. Check whether the affected channel has switched to a fallback backend

Use cases

Read arbitrary web pages and RSS/Atom feeds
Extract YouTube subtitles and search videos
Search and read public GitHub repositories
Search Twitter/X, Reddit, Xiaohongshu, and other platforms after configuring login state
Perform semantic web search through Exa

Supported clients

Claude CodePartial support
OpenClawPartial support
CursorPartial support
WindsurfPartial support