Overview
Ask about visibility, topics, prompts, and competitors right from the terminal while working on the site.
What you can do
These are the jobs the integration is built for.
Check visibility before shipping content changes
While editing pages or copy in the repo, ask Claude Code which tracked prompts are at risk and whether competitors recently moved ahead. Use the answer to decide if the change you are about to commit targets a real AI search gap.
Turn a losing prompt into a concrete edit list
Pick one prompt where mentions dropped, pull competitor context from Beamtrace, and have Claude Code propose specific file or section updates. Keep the whole loop inside your terminal session next to the codebase.
Build an improvement branch from live metrics
Start a fix branch with a short brief generated from current visibility scores, topic gaps, and open improvements. Claude Code can reference the same data as it implements content or metadata changes.
Set up
Connect Claude Code to the shared Beamtrace MCP endpoint, then authorize with your Beamtrace account when prompted.
- Run
claude mcp add --transport http beamtraceand paste the URL below when prompted. - In Claude Code, run
/mcpto verify the server is listed.
MCP endpoint
https://beamtrace.com/api/mcp
Connected apps and their status are listed in Integrations in your dashboard, where you can disconnect access at any time.
Requirements
- A Beamtrace workspace with at least one tracked website.
- A Claude Code setup that allows custom MCP / connector tools.
