get_tech_stack — rankparse mcp MCP Tool Read-only
get_tech_stack
(get tech stack) is one of 73 tools on the
rankparse mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_tech_stack from your client
- Claude Code rankparse mcp get_tech_stack run in your project directory
- Claude Desktop rankparse mcp get_tech_stack ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor rankparse mcp get_tech_stack ~/.cursor/mcp.json
- VS Code rankparse mcp get_tech_stack .vscode/mcp.json
- Zed rankparse mcp get_tech_stack ~/.config/zed/settings.json
- Windsurf rankparse mcp get_tech_stack ~/.codeium/windsurf/mcp_config.json
- Cline rankparse mcp get_tech_stack ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI rankparse mcp get_tech_stack ~/.gemini/settings.json
- Grok rankparse mcp get_tech_stack .mcp.json (in your project root)
- ChatGPT rankparse mcp get_tech_stack Settings → Connectors → Advanced → Developer mode
- Claude.ai rankparse mcp get_tech_stack Settings → Connectors → Add custom connector
- LangChain rankparse mcp get_tech_stack pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http rankparse-mcp https://mcp.rankparse.com/mcp
Other tools on this server
- get_backlinks
- get_referring_domains
- get_outbound_links
- get_domain_authority
- get_domain_rank
- get_anchor_text
- get_top_pages
- get_domain_overlap
- get_link_intersect
- get_similar_domains
- get_competitor_gap
- get_link_audit
- get_sitemap
- get_crawl_history
- get_page_seo
- get_page_performance
- get_site_health
- get_schema_markup
- get_internal_links
- get_link_velocity
- get_new_links
- get_lost_links
- get_site_explorer
- batch_lookup
- check_credits
- get_platform_domains
- get_platform_trends
- list_rank_tracking_sites
- list_tracked_keywords
- get_keyword_rankings
- get_keyword_rank_history
- list_rank_change_alerts
- get_rank_alert_settings
- update_rank_alert_settings
- get_gsc_properties
- get_gsc_top_queries
- get_gsc_top_pages
- get_gsc_page_queries
- get_gsc_query_pages
- get_gsc_date_trends
- get_gsc_country_breakdown
- get_gsc_device_breakdown
- get_gsc_sitemaps
- get_gsc_url_inspection
- get_gsc_query_page_pairs
- get_gsc_page_trend
- get_gsc_query_trend
- get_gsc_opportunity_queries
- get_gsc_low_ctr_queries
- get_gsc_low_ctr_pages
- get_gsc_page_segment
- get_gsc_search_appearance
- get_google_ads_accounts
- get_google_ads_keyword_ideas
- get_google_ads_keyword_metrics
- outreach_create_campaign
- outreach_add_contacts
- outreach_launch_campaign
- outreach_get_campaign
- outreach_suggest_prospects
- outreach_list_campaigns
- outreach_sending_status
- outreach_configure_sending
- outreach_pause_campaign
- outreach_resume_campaign
- zeekeo_list_campaigns
- zeekeo_send_message
- zeekeo_create_template
- zeekeo_create_campaign
- zeekeo_activate_campaign
- provision_indexnow_key
- submit_indexnow_urls
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.