A browser, not a fetch.
Most of what ChatGPT gets asked to explain about a website was never in the HTML to begin with. Enrichr is the part that goes and looks.
A plain fetch gets whatever bytes the server happened to return before any JavaScript ran. On a modern site — React, Three.js, GSAP-driven, anything behind client-side rendering — that's often a shell, not a page. The animations, the WebGL, the design tokens, the hover states, the CSS that actually applied: none of it is in there.
Enrichr opens the real thing in a real browser, lets it fully render, and then reads what's actually there — the live DOM, the computed styles, the running animations, the compiled shaders, the 3D scene graph, sometimes even the original source recovered from a bundle. It hands the useful parts to whatever's asking, packaged as something an LLM can build from rather than just describe.
Why a ChatGPT connector now
Enrichr started as an MCP server for Claude, and the Claude side is still the same product, same tools, same pricing. This site exists because ChatGPT can now connect to remote MCP servers of its own — through Settings → Connectors, signing in with OAuth instead of pasting a key. Same backend, same account, same credits either way; just a setup flow that actually matches how ChatGPT expects a connection to work.
See the connect guide for the exact steps, or the Claude-side about page for a more, well, cinematic tour of the same idea.
Free to start — 25 credits every month, no card required.