seo-ranking docs — profullstack-mcp MCP Resource
seo-ranking docs
is one of 53 resources on the
profullstack-mcp
MCP server. Connect the server and your client can attach it as context.
by client
How to attach seo-ranking docs from your client
- Claude Code profullstack-mcp Resource/seo-ranking docs run in your project directory
- Claude Desktop profullstack-mcp Resource/seo-ranking docs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor profullstack-mcp Resource/seo-ranking docs ~/.cursor/mcp.json
- VS Code profullstack-mcp Resource/seo-ranking docs .vscode/mcp.json
- Zed profullstack-mcp Resource/seo-ranking docs ~/.config/zed/settings.json
- Windsurf profullstack-mcp Resource/seo-ranking docs ~/.codeium/windsurf/mcp_config.json
- Cline profullstack-mcp Resource/seo-ranking docs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI profullstack-mcp Resource/seo-ranking docs ~/.gemini/settings.json
- Grok profullstack-mcp Resource/seo-ranking docs .mcp.json (in your project root)
- ChatGPT profullstack-mcp Resource/seo-ranking docs Settings → Connectors → Advanced → Developer mode
- Claude.ai profullstack-mcp Resource/seo-ranking docs Settings → Connectors → Add custom connector
- LangChain profullstack-mcp Resource/seo-ranking docs pip install langchain-mcp-adapters
Other resources on this server
- template
- template docs
- template examples
- readme-badges
- readme-badges docs
- readme-badges examples
- craigslist
- seo-ranking
- seo-ranking examples
- wcag
- wcag examples
- scanner
- scanner docs
- scanner examples
- example
- social-poster
- social-poster docs
- social-poster examples
- fake_json
- fake_json docs
- fake_json examples
- tides-currents
- crypto-badge docs
- crypto-badge examples
- link-shortener
- qr-generator
- qr-generator examples
- lighthouse
- lighthouse docs
- lighthouse examples
- test-module
- weather
- weather examples
- health-check
- backlinks
- backlinks docs
- backlinks examples
- email_checker
- email_checker docs
- email_checker examples
Read from the server itself, by connecting to it and calling resources/list on 11 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.