Conqueror

com.conquerorappPublished by conquerorapp.comOfficial publisherv0.0.14Updated Oct 25, 2026

Turns SEO insight into page changes: keyword research, SERP and rank data, rewrites you approve.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Conqueror is a remote SEO MCP server that gives an assistant live keyword, SERP and rank data to research terms, map them to pages and propose rewrites.

What you can do
Research keywords and score opportunities by volume, difficulty, intent and SERP reality, and cluster them into page-level groups with cannibalization flags. Study competitors and the competitive landscape, including ranking keywords, content themes and backlinks. Find link prospects from SERPs and competitor backlinks, surface public contact paths and draft outreach. Rewrite a WordPress page for a target keyword and propose it as a diff for review before anything goes live.
When to use it
Use it when you want an assistant to run repeatable SEO workflows — keyword research, clustering, competitor analysis, link prospecting or page rewrites — against live Conqueror data rather than guesswork.
Requirements
A remote MCP endpoint with OAuth sign-in; a Conqueror account is required. The page-rewrite workflow also needs a connected WordPress site. The companion skills are installed separately through an npm command or by copying folders into the agent's skills directory.
Before you install
The rewrite workflow changes a WordPress page, though it proposes a diff and applying it is a click in Conqueror. Link prospecting collects public contact details and drafts outreach messages. The README states the skills never publish, apply or spend without asking, but review proposed changes before applying them.

Installation

In SourceWeft

  1. Open Conqueror in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.conquerorapp%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "conqueror": {
      "type": "http",
      "url": "https://winwith.conquerorapp.com/mcp"
    }
  }
}

README

Conqueror Agent Skills

SEO workflows for Claude Code, Codex, and other AI agents that support SKILL.md.

Each skill hands your agent one repeatable job — find keywords worth targeting, map them to pages, study a competitor, rewrite a page to win a term — using live data from Conqueror.

Connect Conqueror MCP first

These skills do nothing on their own. They tell your agent which workflow to run; the data comes from the Conqueror MCP server. Connect it before installing anything:

https://winwith.conquerorapp.com/mcp

In Claude Desktop or Claude Code, add that as a remote MCP server and sign in when prompted. You need a Conqueror account — start free.

Install

sh
npx skills add Shipper-dot-now/conqueror-skills

Pick the skills and agents you want interactively, or take everything:

sh
npx skills add Shipper-dot-now/conqueror-skills --skill '*'

Scope it to one agent with --agent claude-code or --agent codex.

To install by hand instead, copy the folders into your agent's skills directory:

sh
git clone https://github.com/Shipper-dot-now/conqueror-skills.git
mkdir -p ~/.claude/skills && cp -R conqueror-skills/skills/* ~/.claude/skills/   # Claude Codemkdir -p ~/.codex/skills  && cp -R conqueror-skills/skills/* ~/.codex/skills/    # Codex

The skills

Start here if you're new:

SkillWhat it does
/conqueror-seo-project-setupSets up a durable local workspace — working folder, site scope, goals, positioning, and Search Console intake — so your agent keeps context between sessions.
/conqueror-seo-coachExplains what each workflow does and recommends the next step. Use it when you're not sure what to run.

Research:

SkillWhat it does
/conqueror-keyword-researchTurns seed topics into a prioritized opportunity set, scored on volume, difficulty, intent, and SERP reality.
/conqueror-keyword-clusteringGroups keywords into page-level clusters, maps each to an existing or new page, and flags cannibalization.
/conqueror-competitive-landscapeMaps who wins a market, which content is working, and where the openings are.
/conqueror-competitor-analysisDeep dive on one competitor — ranking keywords, content themes, backlinks, weaknesses.

Act on it:

SkillWhat it does
/conquer-keywordRewrites your WordPress site's best-matching page for a target keyword and proposes it as a diff you review before anything goes live. Needs a WordPress connection.
/conqueror-link-prospectingFinds link prospects from SERPs and competitor backlinks, digs out public contact paths, and drafts the outreach.

How they work

A skill is a markdown file. Your agent reads it when you run the matching slash command, then follows the workflow using the Conqueror MCP tools it describes. Nothing is compiled or executed — you can read every one of these files in a couple of minutes, and you should.

The skills never publish, apply, or spend on your behalf without asking. /conquer-keyword proposes a diff; applying it is your click in Conqueror.

To learn how skills work in your agent:

License

MIT — see LICENSE.

Source: README.md at commit 5e06491

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.0.14LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts