MCP Cookbook
The reference lists every tool. This is how to get the most out of it: compose Trakkr with the other MCP servers you already run, so a finding turns into a shipped fix in one conversation.
Trakkr is the eyes, your other tools are the hands
Trakkr never touches your website. By design, it measures and recommends; it does not publish, commit, or post. That sounds like a limit. It is the opposite. It means Trakkr composes cleanly with the tools you already trust to make changes. You keep one connection that watches your AI visibility, and the editor, repo, or CMS you already use does the writing, all in the same chat.
Every recipe below is the same three-move loop:
Trakkr finds the gap and the fix
Your other MCP makes the change
Trakkr confirms it landed
Recipes
Each one pairs Trakkr with a second MCP you already run. Jump to your tool, or browse by how you work. The first set needs no setup at all: just connect Trakkr and chat.
Build your own recipe
The loop generalises. Any MCP server that can write something is a pair for Trakkr. Diagnose with a Trakkr tool or attach a trakkr:// resource, hand the result to the tool that does the work, then re-read Trakkr to confirm. One thing to remember: most changes are detected when the daily research run completes, so the verify step is a next-day check, not a live refresh.
Want the full surface? The MCP server reference lists every tool, resource and slash-command workflow. The product tour shows it running inside Claude, ChatGPT and Cursor.