Introducing the MyBacklinks CLI

MyBacklinks now ships an official npm package: @mybacklinks/cli.

The CLI uses the same backend tool surface as the dashboard and MCP server, so terminal workflows, AI agents, and product UI stay aligned instead of drifting into separate implementations.

What You Can Do

• Log in with OAuth portal flow or --api-key
• Check account status, subscription, credits, and upcoming fields
• List projects and backlink resources
• Create or update backlink resources
• Fetch or update project backlink records
• Run domain research for backlinks, DR, and traffic

Install

npm install -g @mybacklinks/cli

Authenticate

mybacklinks login
mybacklinks login --api-key mbk_xxxxx

Example Commands

mybacklinks status
mybacklinks list-projects
mybacklinks fetch-project-info --project-id <project-id>
mybacklinks fetch-project-backlinks --project-id <project-id> --status indexed
mybacklinks fetch-backlinks-by-domain --domain competitor.com --limit 100 --dofollow
mybacklinks fetch-dr-by-domain --domain competitor.com
mybacklinks fetch-traffic-by-domain --domain competitor.com

Credit Model

Low-cost account and project operations do not consume credits.

High-cost external domain research commands do consume credits:

• fetch-backlinks-by-domain
• fetch-dr-by-domain
• fetch-traffic-by-domain

Use mybacklinks status before running bulk research so the remaining balance is explicit.

Why This Matters

The CLI is not a side channel. It is part of the same automation surface as MCP:

• same auth model
• same canonical tools
• same project and backlink semantics
• same credit-aware domain research

That makes it practical to move between manual dashboard work, terminal scripts, and AI-agent workflows without rewriting everything.