seo-mcp-server
MCP · SEO
Talk to your site's SEO. It crawls, audits every page, reads your real Search Console data and measures Core Web Vitals — and explains it in plain language.
Not everything we make is for sale. We release the tools we needed and could not find as open source: free to read, run, fork and break. If it saves someone a weekend, it was worth shipping.
8 tools, all running on our own infrastructure before they were published. The numbers come from GitHub, not from a hand-typed list.
Talk to your site's SEO. It crawls, audits every page, reads your real Search Console data and measures Core Web Vitals — and explains it in plain language.
Award-grade motion for the web with zero dependencies. 33 components: scroll reveals, text animations, page transitions and a custom cursor — plus an MCP server so Claude and Cursor use them instead of improvising.
Talk to your Proxmox cluster in plain language: list nodes, VMs and containers, and control lifecycle or snapshots — safely.
Chat with your Docker host. An MCP server with a panel and a terminal to run Docker and Compose, metrics included.
Inventories your VMware, checks compatibility, estimates the cost of moving to Proxmox and produces the report. For leaving licences behind knowing what is ahead.
Living infrastructure documentation: agentless discovery that draws the map of your real network and tells you what changed.
Open-source email security: a self-hosted mail client with an antivirus layer. Detects phishing, malware and impersonation, and leaves you the report.
Self-hosted, end-to-end encrypted password manager: command line, terminal, web and browser extension. Your keys never leave your machine.
Every studio ends up rewriting the same animations on every project. We pulled ours into one place, sharpened them and published them: 33 components with zero dependencies — scroll reveals, text animations, page transitions and a custom cursor.
And it ships an MCP server: Claude or Cursor read the catalogue and use these components instead of improvising a different animation every time. The same idea as the rest of this page, applied to design.
A translator. On one side an assistant that understands what you ask for; on the other, your infrastructure, which only understands exact commands. The MCP server sits between them and decides what may happen and what may not.
“how many VMs are stopped on node 2?”
translates, checks permissions and logs everything
this is what we publishProxmox, Docker, your network, your mail
The middle box is the whole point: the assistant never touches your infrastructure directly. It goes through something you control, with the permissions you grant, and it writes down everything it does.
Every repo started as our own problem on a Tuesday afternoon. Publishing it costs nothing extra and saves someone else writing it from scratch.
A tool that touches your infrastructure should not be a black box. If you are giving it access to your cluster, you deserve to see what it does.
The bugs strangers find are the ones we would never have seen. It is the best QA there is, and it is free.
Everything ships with Docker Compose and an example file. No sign-up, no API key of ours, no phoning home.
No permission, no payment. Including if you bill for it.
Fork it, cut what you do not need, add what you do. Nothing to send back.
Published as is. Before it touches production, test it the way you would test anything.
We read issues and answer when we can, but there is no SLA. If you need a safety net, that is a service.
These tools were built for our own problems. If yours looks similar, we adapt them, install them where you say and teach you to run them.
On your server, your cloud or your basement. Nothing leaves where you say.
To your systems, your permissions and the way you actually work.
Documentation in your language and a session with the team.
If you want. If not, it keeps running and it is yours anyway.
Yes. Open licence, no hidden “pro” tier, no features held back waiting for a card. What you see on GitHub is what there is.
No. It runs where you install it and talks to what you point it at. No telemetry, no calls to any server of ours.
Yes, including for money. The licence allows it and we are glad: that is why it is published.
Open an issue on GitHub with what you did and what happened. If it is a security issue, email first instead of publishing it.
Yes. Pull requests welcome. For big changes, open an issue first so you do not build something we cannot merge.
It installs with Docker Compose alone, but if you would rather not wrestle with it, we set it up and hand it over running. That is a service, and it is quoted to measure.
No strings. Whether or not you hire us, you leave with a concrete list of fixes for your site.
Book 20 min