
Rankgoat
io.github.madrzakPublished by GitHub account madrzakv0.5.1Updated Oct 27, 2026
SEO for AI agents: plan content, publish posts, earn dofollow backlinks, track Domain Rating.
Overview
RankGoat MCP server that lets an assistant manage SEO content plans, generate and approve blog posts, and read backlink and Domain Rating data.
- What you can do
- Manage account and sites: view member details, list sites, check credit balances
- Plan and schedule content briefs, including AI-assisted planning and archiving
- Generate, read and approve blog posts, and poll background jobs
- Review backlinks, mentions, Domain Rating history, on-page and sitemap SEO, Search Console data, link equity and flywheel fixes
- Maintain content hubs and product feature lists that ground generated posts
- When to use it
- Useful when you run RankGoat's backlink exchange and want an assistant to draft, schedule and approve posts or pull SEO metrics without leaving the chat. Also suits CI or scripted workflows that need structured JSON output.
- Requirements
- Runs locally via npx with Node.js 20 or newer. Needs a RankGoat account and an API key supplied through the RANKGOAT_API_KEY environment variable (or the CLI's login or --api-key option). Network access to the RankGoat API.
Installation
In SourceWeft
- Open Rankgoat in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
RankGoat CLI
The official command-line interface for RankGoat, the SEO backlink exchange that writes and publishes done-for-you blog posts with real dofollow links between member sites.
Manage your content plan, generate posts, approve drafts, and read your backlink and SEO data straight from the terminal or a CI pipeline. Built on the public RankGoat API.
Install
Or run it without installing:
Requires Node.js 20 or newer. Zero runtime dependencies.
Authenticate
Create an API key at rankgoat.app/app/settings#api, then:
The key is stored in ~/.rankgoat/config.json (owner-readable only). Alternatively set RANKGOAT_API_KEY in your environment, or pass --api-key on any command, handy for CI.
Usage
Account & sites
Content plan
The monthly plan is a calendar of briefs the AI turns into posts.
Posts
Backlinks & SEO
Content hubs
Topic clusters the monthly planner draws briefs from, weighted by priority.
Product features
Your product's real capabilities. They ground content generation, so posts never invent features the product does not have.
Jobs
Some actions (AI planning, post generation) run in the background and return a job handle. Poll it, or pass --wait on the original command:
Options
Scripting
Every command supports --json for machine-readable output:
Exit code is non-zero on any API or usage error, so it composes cleanly in CI.
For AI agents
The CLI is built to be driven by agents: structured JSON on every command, env-var auth, and non-zero exits on failure. Two ways to plug in:
MCP server. rankgoat mcp runs a Model Context Protocol server on stdio exposing all 34 capabilities (plan, generate, approve, backlinks, mentions, DR, GSC, sitemap, hubs, features, link equity, flywheel) as typed tools:
Or in any MCP client config:
Shell + SKILL.md. Agents that run shell commands can use the CLI directly; the bundled SKILL.md teaches them the workflows, including which calls spend credits and where to keep a human in the loop.
More at rankgoat.app/agent.
How RankGoat works
RankGoat members pay for done-for-you blog posts that get published on their own sites with dofollow outbound links to other members. The link graph is non-reciprocal and niche/DR-matched, so it builds real authority without pattern-matching as a scheme. Learn more at rankgoat.app or read the API reference.
License
Source: README.md at commit 4d720a7
Tools
0Version history
1- v0.5.1LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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