MIT-licensed tool connects coding agents for reciprocal link trades

• Builders Backlinks puts a one-for-one reciprocal link trade inside an MCP server. nicklaunches' workflow post says the agent can register a site, take a match, write the link into a repository, and verify it is live.
• The project is free and MIT-licensed, and nicklaunches' install post lists Claude Code, Cursor, Codex, and Gemini CLI as connection targets.
• Matching keeps partner domains hidden until both sides accept. In nicklaunches' follow-up, the creator described category-based matching, no cash in the exchange, and an agent writing the agreed link into its owner's repo.
• The network was still small on the creator's latest count: nicklaunches' network update reported 58 builders, 56 sites, and members in 19 categories.

The open-source repository frames the product around a mundane failure point: an agent is already working in the repository where a promised link must be placed. Its MCP documentation describes 11 tools, but deliberately leaves the actual edit, commit, and deployment to the coding agent already attached to that repo.

The published MCP docs describe a hosted Streamable HTTP endpoint, not a locally installed package or binary. Three tools work without credentials, while a bearer key unlocks the eight tools that act on a member's own listings and matches.

1. get_rules, get_categories, and search_partners let an agent inspect the exchange anonymously.
2. submit_site fetches a homepage, looks up Domain Rating, and drafts a listing.
3. A second, confirmed submit_site call creates the listing and runs an immediate matching pass.
4. list_matches returns a masked proposed partner.
5. respond_to_match accepts or declines the proposal.
6. get_link_brief returns a target URL, approved anchor options, and a paste-ready HTML, Markdown, MDX, or JSX snippet after agreement.
7. mark_link_placed, check_links, and get_my_standing handle the live-link record after placement.

The MIT license covers the code. The docs confirm Claude Code and Cursor against the server, while calling the Codex CLI and Gemini CLI configurations untested, should-work examples.

The first site-submission call writes nothing. The server produces a category, Domain Rating, suggested anchors, and an identity-scrubbed description, then requires a human confirmation before it lists the site, according to the tool reference.

Anonymous searches expose the category, DR, description, desired anchors, offered placement, and give-versus-receive count, but no partner domain, URL, or email. Mutual acceptance reveals both sides' domains and emails at the same instant; only then can either request the link brief.

A proposed match expires after 14 days. The documentation also says descriptions, anchors, and DR are public to anonymous searchers, and that revealing a domain to an accepted partner cannot be undone.

After agreement, the brief gives the coding agent a link snippet in the repository's format. The MCP server has no tool for editing the page itself: the docs describe the already-connected agent finding a relevant page, writing a sentence around the link, committing, and deploying.

mark_link_placed then fetches the submitted page and reports the detected anchor, dofollow or nofollow status, sitewide appearance, and placement class: content, footer, navigation, sidebar, or unknown. A match reaches placed only after both reciprocal links verify live; checks recur at day 7, day 30, and monthly.

A crawl failure is returned as inconclusive rather than as a missing link. The server reads rendered HTML, so a JavaScript-injected link can be live yet initially unconfirmed.

The creator's August 22 snapshot counted 58 builders trading links across 56 sites. The attached category chart put Launch Platforms at eight sites, Marketing at seven, Food & Drink at six, SEO at five, and AI and Developer Tools at four each.

CMS, DevOps, Security, Writing, and Web3 were among the categories he said had no member yet. The same update said 18 categories were empty.