# Wincher MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Wincher MCP

Track keyword rankings, SERPs, competitors and search performance history

- Record: https://musedirectory.ai/connector/wincher-mcp
- Category: Marketing & Ads
- Developer: usefulapi (https://usefulapi.io/wincher/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 65ms, checked 2026-10-29T10:45:49Z
- Endpoint: https://wincher.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T12:51:29Z)
- Source: Found in the official MCP Registry (io.usefulapi/wincher) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fwincher

Connects to Wincher SEO tracking platform. Read keyword rankings, search results, competitor data and historical trends. Add keywords, organize them into groups, and annotate ranking changes for your tracked websites.

Example request: "Show me how my top keywords ranked last month compared to my competitors"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Wincher MCP to help me. It is a free service with an MCP server at https://wincher.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- wincher_get_account: The Wincher account behind the token: id, timezone and the plan limits with current usage (websites, users, keywords, keyword lookups, map-tracking credits, history days). Check keyword usage here before adding keywords. GET /account.
- wincher_get_user: The Wincher user the token belongs to: id, role, state, project access and profile (name, email, language). GET /user.
- wincher_list_search_engines: The search engines Wincher can track (id, domain such as google.com, country, languages, default location). GET /search-engines.
- wincher_search_locations: Search the locations Wincher can track rankings for (code, name, country), most popular first, at most 100. Both are required by the API: an ISO country code and a free-text search (at least 3 characters). GET /locations.
- wincher_list_projects: List projects (folders that group websites): id, name, website_ids, user_ids, and optionally the ranking summary for a period. GET /projects.
- wincher_list_websites: List the websites tracked in Wincher: id, domain, display name, search engine, location, language, mobile flag, keyword/group/competitor counts, competitors and brand keywords. Optionally with the ranking summary for a period. GET /websites.
- wincher_get_website: One tracked website with its settings, competitors, brand keywords, counts and (for the period) ranking summary. GET /websites/{website_id}.
- wincher_list_keywords: List the keywords tracked for a website with groups, volume, CPC, difficulty, competition, search intents and, with include_ranking, the latest position, traffic, ranking pages, SERP features and best position in the period. Positions are tracked down to the top 30. GET /websites
- wincher_get_keyword: One tracked keyword with its groups, volume, CPC, difficulty and (default) ranking for the period. GET /websites/{website_id}/keywords/{keyword_id}.
- wincher_get_keyword_serps: The most recent search result pages Wincher stored for a keyword (up to 30): date, search volume, SERP features and the ranking results (position, URL, domain, traffic). GET /websites/{website_id}/keywords/{keyword_id}/serps.
- wincher_get_keyword_ranking_history: Historical position (or estimated traffic) for ONE keyword as time series, optionally split per ranking page or per competitor. GET /websites/{website_id}/keyword/{keyword_id}/ranking-history.
- wincher_get_ranking_history_bulk: Historical positions for up to 50 keywords at once (one time series per keyword). This is a read: it uses POST only because the keyword id list goes in the body. POST /websites/{website_id}/ranking-history.
- wincher_list_groups: List the keyword groups of a website: id, name, keyword_ids, average difficulty, search-intent counts and optionally ranking summaries. GET /websites/{website_id}/groups.
- wincher_get_group: One keyword group with its keyword ids and (optionally) ranking summary for the period. GET /websites/{website_id}/groups/{group_id}.
- wincher_list_competitors: The competitor domains tracked for a website (id, domain, created_at). GET /websites/{website_id}/competitors.
- wincher_list_competitor_ranking_summaries: Ranking summaries (average position, share of voice, traffic, position distribution, volume) for the website's competitors over a period, for comparison with your own. GET /websites/{website_id}/competitors/ranking-summaries.
- wincher_list_competitor_keyword_positions: For each tracked keyword, the position of your site and of each competitor in the period. GET /websites/{website_id}/competitors/keyword-positions.
- wincher_list_annotations: The annotations (notes on the ranking graphs: automatic, alert and user-written) for a website, optionally within a period. GET /websites/{website_id}/annotations.
- wincher_list_segments: The saved segments (keyword filters) usable as segment_id in other tools. By default also temporary ones; only_named limits to saved ones. GET /segments.
- wincher_add_keywords: WRITE: start tracking up to 50 new keywords on ONE website. EACH keyword uses one keyword slot of the plan's keyword quota (see wincher_get_account), and it is tracked and updated from then on; this tool cannot remove keywords again. Each keyword may name a preferred_url (the lan
- wincher_create_group: WRITE: create a keyword group on a website, optionally containing existing keywords (ids from wincher_list_keywords). Uses no keyword quota. POST /websites/{website_id}/groups.
- wincher_create_annotation: WRITE: add a user annotation (a note shown on the ranking graphs, e.g. 'Launched new landing page') for a date, optionally tied to specific keywords; without keyword_ids it is a global note for the website. Visible to everyone with access to the website. Uses no keyword quota. PO

Screening checks:
- MCP handshake: pass (Answered in 7ms)
- Domain against threat feeds (Cloudflare security DNS): pass (wincher.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (22 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)