From 6995c4993734b4ef73fd0d567efe35e464815e1c Mon Sep 17 00:00:00 2001
From: jonastmb <20173713+kopachlager@users.noreply.github.com>
Date: Fri, 24 Jul 2026 00:28:00 +0300
Subject: [PATCH] cross-link developer tools

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index b3b4bb5..a31082e 100644
--- a/README.md
+++ b/README.md
@@ -10,6 +10,8 @@ Open-source diagnostics for checking what public websites return to crawlers.
 
 The CLI inspects returned HTML, compares standard and crawler user-agent HTTP responses, and validates common discovery files. It does not render JavaScript, change a website, require a Prerender Buddy account, or predict search rankings, indexing, AI citations, mentions, or traffic.
 
+Using an AI assistant? The [`prerenderbuddy-mcp`](https://github.com/kopachlager/prerenderbuddy-mcp) repository exposes these diagnostics through a local stdio MCP server. See the [Prerender Buddy tools overview](https://prerenderbuddy.com/developer-tools) to compare the CLI, MCP server, Chrome extension, and managed service.
+
 Run it without installing:
 
 ```bash
@@ -241,6 +243,8 @@ Read [CONTRIBUTING.md](./CONTRIBUTING.md). Keep contributions focused on accurat
 
 ## Next steps
 
+- Use the [MCP server](https://github.com/kopachlager/prerenderbuddy-mcp) with compatible AI assistants.
+- Compare all [Prerender Buddy developer tools](https://prerenderbuddy.com/developer-tools).
 - Run the [browser-based crawler checker](https://prerenderbuddy.com/tools/bot-view-checker).
 - Read the [technical documentation](https://prerenderbuddy.com/docs).
 - Review the [public roadmap](./ROADMAP.md).