github_repo_seo_audit — agent web reader MCP Tool
github_repo_seo_audit
(github repo seo audit) is one of 3 tools on the
agent web reader
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call github_repo_seo_audit from your client
- Claude Code agent web reader github_repo_seo_audit run in your project directory
- Claude Desktop agent web reader github_repo_seo_audit ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agent web reader github_repo_seo_audit ~/.cursor/mcp.json
- VS Code agent web reader github_repo_seo_audit .vscode/mcp.json
- Zed agent web reader github_repo_seo_audit ~/.config/zed/settings.json
- Windsurf agent web reader github_repo_seo_audit ~/.codeium/windsurf/mcp_config.json
- Cline agent web reader github_repo_seo_audit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agent web reader github_repo_seo_audit ~/.gemini/settings.json
- Grok agent web reader github_repo_seo_audit .mcp.json (in your project root)
- ChatGPT agent web reader github_repo_seo_audit Settings → Connectors → Advanced → Developer mode
- Claude.ai agent web reader github_repo_seo_audit Settings → Connectors → Add custom connector
- LangChain agent web reader github_repo_seo_audit pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-web-reader https://x402.charliemorrison.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.