Peecockpit is the full-funnel GEO operating system: six per-URL data sources joined on the canonical URL, exposed over MCP, routed to the team that can move the metric. Built by one person, for the Peec MCP Challenge, in public.
Enterprise SEO consultant. Working with brands that publish at scale (sometimes 50M+ pages) on how to stay visible as the search funnel splits between Google and the AI assistants. Has ranked websites in every country of the world, including Christmas Island.
Peecockpit is the cockpit Jan-Willem wished existed for client work: every gap routed to an owner, every action emitting a tracked_id, every retrack closing the loop. The architecture and visual surface are built around a real consulting workflow, not a demo script.
Four tools shipping in parallel with Peecockpit. Same person, same stack, same opinion: every signal an SEO or GEO team needs should be one MCP call away.
Peec opened up its MCP and asked the community to build something useful on top of it. Peecockpit is the answer: a full-funnel GEO operating system that orchestrates four interoperating MCP servers (Peec, Ahrefs, GSC Wizard, Glippy) plus three wrapped APIs (Ahrefs Firehose, Majestic, BotsAnalyser).
Every page in Peecockpit fetches from a single composite MCP tool. The tool is the join. Agents call it; humans see it; both get the same payload. That contract makes the rest of the work possible.
Every recommendation emits a tracked_id and is retracked at T+14 / T+28. The outcome delta closes the loop. The differentiator vs. snapshot reporting is here, not in the visuals.
The semantic-gap pipeline runs on multilingual-e5-large-instruct, so non-English markets are first-class. Most US-built tools miss this. For Jan-Willem's client base, it's the day-one feature.
Peec's create_prompt / create_brand / create_tag / create_topic land in the write-queue, gated by an explicit opt-in and bounded by a daily apply cap. Read-only would be the failure mode of this submission.
Each surface carries chips showing live MCP / file snapshot / fallback, so the freshness of every number is explicit on the page.
The full repo, planning docs, architecture notes, and design rationale are public on GitHub. The website is generated from one zero-dependency Node script. Nothing here is a black box.
If you run an SEO or GEO program (agency, in-house, or enterprise) and any of this resonates, the fastest way to reach me is LinkedIn. I read every message and reply within a day or two.
You'll get an invite when we open the next batch, plus one short email when we ship a new feature page. No drip campaign, no spam.
Early-access invites go out in small batches. Unsubscribe anytime.