request_indexing — SEOPro AI MCP Tool
request_indexing
(request indexing) is one of 18 tools on the
SEOPro AI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call request_indexing from your client
- Claude Code SEOPro AI request_indexing run in your project directory
- Claude Desktop SEOPro AI request_indexing ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SEOPro AI request_indexing ~/.cursor/mcp.json
- VS Code SEOPro AI request_indexing .vscode/mcp.json
- Zed SEOPro AI request_indexing ~/.config/zed/settings.json
- Windsurf SEOPro AI request_indexing ~/.codeium/windsurf/mcp_config.json
- Cline SEOPro AI request_indexing ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SEOPro AI request_indexing ~/.gemini/settings.json
- Grok SEOPro AI request_indexing .mcp.json (in your project root)
- ChatGPT SEOPro AI request_indexing Settings → Connectors → Advanced → Developer mode
- Claude.ai SEOPro AI request_indexing Settings → Connectors → Add custom connector
- LangChain SEOPro AI request_indexing pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http seo-agent https://api.seoproai.co/api/mcpOther tools on this server
- list_websites
- get_website_stats
- get_search_performance
- get_top_search_keywords
- get_search_trends
- get_ai_search_traffic
- run_seo_audit
- check_ai_citations
- get_backlink_profile
- get_keyword_plan
- generate_keyword_plan
- generate_article
- get_article_status
- list_articles
- get_article
- publish_article
- get_indexing_status
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.