SaaS LinkrSaaS Linkr

Developer Docs.
Agent Setup.
MCP Protocol.

Complete technical specifications and 1-minute setup guides for Cursor, Claude Desktop, Claude Code, Windsurf, and Antigravity.

Connect in 60 Seconds

Choose your AI IDE or agent to view the one-click MCP server configuration.

GitHub App / Zero-Touch Autopilot

Connect your GitHub repository in your Founder Dashboard. On the 1st of every month, we automatically create a clean branch and open a ready-to-merge Pull Request with your 1,800+ word partner article.

Configuration
# Zero code required.
# 1. Open Founder Dashboard -> Integrations
# 2. Connect your GitHub repository & specify your blog folder (e.g. content/blog)
# 3. Every month, click "Merge" on the automated Pull Request. Total effort: 5 seconds.
Example AI Agent Prompt

"No prompts needed. SaaS Linkr opens automated Pull Requests directly to your repository."

MCP Tool Specifications

The standard MCP tools exposed by the @saaslinkr/server package.

get_pending_matches

MCP Tool

Fetches the current month’s assigned partner SaaS matches, including target URLs, anchor text keywords, domain rating delta, and assigned topics.

ParametersNone (Authenticated via SAASLINKR_API_KEY)
Return OutputArray of EditorialMatch objects with target SaaS details and publication deadlines.

generate_article

MCP Tool

Produces a comprehensive, 1,800+ word contextual editorial markdown draft seamlessly embedding the target partner anchor text and URL.

Parametersmatch_id (string), blog_framework (string, optional: "nextjs" | "astro" | "hugo")
Return OutputFull markdown string with formatted YAML frontmatter (title, description, date, author, tags).

verify_published_article

MCP Tool

Crawls a live published URL to verify that the partner do-follow backlink is indexable, contains the agreed anchor text, and has no nofollow/ugc tags.

Parametersmatch_id (string), article_url (string)
Return OutputVerification result (verified_dofollow | missing_backlink) and timestamped audit report.

3-Way Triangular Loop Safety

Why our non-reciprocal triangular architecture prevents reciprocal footprint penalties.

01. Partner A → Partner B

Site A drafts an in-depth 1,800+ word technical article on their blog embedding a natural do-follow editorial mention for Site B.

02. Partner B → Partner C

Site B writes a matching article for a third independent software tool (Site C) in a complementary niche.

03. Partner C → Partner A

Site C closes the loop by publishing a verified editorial backlink pointing back to Site A. Search engines see 100% natural, one-way editorial citations.

Developer & MCP FAQ

Technical answers regarding local agent execution and security.

Traditional link exchanges require invasive GitHub app permissions, database access, or clumsy CMS plugins. With MCP, your local AI coding agent (running inside Cursor or Claude) understands your exact repository, file structure, and frontmatter schema, writing clean markdown directly to your blog.