Read Wincher keyword rankings, SERPs, competitors and history; add keywords, groups and notes. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"wincher": {
"url": "https://wincher.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"wincher": {
"type": "http",
"url": "https://wincher.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Wincher Personal Access Token.
Create it in Wincher → Account → Personal Access Tokens. The Wincher API is part of the higher paid plans. The token acts with your user's permissions and is used only to call the Wincher API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Wincher Personal Access Token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
wincher_get_account | read | Get account and plan limits 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 | read | Get current user The Wincher user the token belongs to: id, role, state, project access and profile (name, email, language). GET /user. |
wincher_list_search_engines | read | 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 | read | Search tracking 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 | read | 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 | read | List tracked 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 | read | 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 | read | 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/{website_id}/keywords. |
wincher_get_keyword | read | 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 | read | 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 | read | 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 | read | Get ranking history for several keywords 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 | read | List keyword 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 | read | Get keyword 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 | read | List competitors The competitor domains tracked for a website (id, domain, created_at). GET /websites/{website_id}/competitors. |
wincher_list_competitor_ranking_summaries | read | 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 | read | 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 | read | 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 | read | 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 | Add keywords to track 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 landing page expected to rank). Invalid or already-tracked keywords are ignored by Wincher (not created). 'groups' are keyword group NAMES to put every keyword in (may be empty; use names from wincher_list_groups, an unknown name may create a new group). POST /websites/{website_id}/keywords/bulk. |
wincher_create_group | write | Create keyword 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 | 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. POST /websites/{website_id}/annotations. |
wincher_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
wincher_request_feature | Request a missing feature Tell usefulapi that the user needs something the Wincher tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
wincher_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Wincher tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
wincher_cancel_subscription | Cancel the Pro subscription Cancel the caller's Wincher Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run wincher_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited |
Pro covers this Wincher server only. Subscribe with wincher_upgrade (it returns a Stripe Checkout link). Cancel any time with wincher_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running wincher_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Wincher. The server calls the Wincher API with your own Wincher access, so it sees only the data that your account can see.
The login page asks for your Wincher Personal Access Token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Wincher Personal Access Token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Wincher API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Wincher.
Yes, if you approve it. 3 of the 22 Wincher tools can create or change data. The other 19 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Wincher server only. Run wincher_usage_status to see how many calls you used.
Ask the AI to run wincher_upgrade: it returns a Stripe Checkout link. To cancel, run wincher_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with wincher_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.