Set up LinkDR in your agent

You can start from either path. Most people try checkout first because it needs no admin account.

Before you begin

You need:

• An AI client that can fetch a URL (Cursor, Claude, Grok, Codex, and similar)
• A LinkDR login for checkout, or an admin LinkDR login for research MCP
• A target site if you are ordering, or a brand / keyword if you are researching

The public skill files do not require login. Paying does. Research tools require login plus admin.

1. Order backlinks

Paste this into the agent:

Fetch https://linkdr.com/SKILL.md and follow it to plan my backlink order

Then give it a URL and a budget, for example:

Target https://genppt.com. About $700. Prefer DR 40. Auto-approve is fine.

The agent should come back with one /agent/checkout?... link, not a multi-step wizard. Open the link in a browser, sign in if asked, and pay.

If it tries to walk /onboarding page by page, point it back at SKILL.md. That file is the contract.

More detail: Managed backlinks.

2. Connect research MCP

This step is for admins.

In Cursor, Grok, Claude, or another MCP client, add a server with only this URL:

{
  "mcpServers": {
    "linkdr": {
      "url": "https://linkdr.com/mcp"
    }
  }
}

Do not add an Authorization header. The client should see 401, open a browser, and take you through LinkDR sign-in and Allow.

When that succeeds, try:

Call get_domain on genppt.com and tell me what you got.

If you see a miss, we do not have that host. Try a keyword next, or fetch keyword fan-out.

Running the app locally? Use http://localhost:3000/mcp instead.

How sign-in works: Auth.

3. Attach a research skill

MCP gives the agent tools. A skill tells it the order to call them.

• Keyword fan-out for brand → SERP → listicles and creators
• YouTube outreach when you only care about ranking videos

Fetch the skill file in the same chat as the MCP connection so the agent does not improvise a crawl of the live web.

Next steps

• Connect MCP if you want the tool catalog before a skill.
• Tools for arguments and empty-result behavior.
• Troubleshooting if sign-in never opens or you get 403.