Overview
Visibility, prompt performance, and competitor context are available right in the terminal.
What you can do
These are the jobs the integration is built for.
Answer visibility questions mid-session
Without leaving Codex CLI, ask how your AI visibility score moved, which competitors gained rank, or which prompts need attention. Useful when you are already in a coding flow and do not want to context-switch to the dashboard.
Investigate a topic gap from the terminal
When you suspect a product page is underperforming in AI answers, pull prompt-level detail and competitor mentions directly in Codex. Follow up in the same session with code or content changes.
Prioritize what to fix next
Ask Codex to rank open improvements and losing prompts by impact, then use that ordered list to plan the rest of your session. Beamtrace stays available as context for every follow-up question.
Set up
Connect Codex CLI to the shared Beamtrace MCP endpoint, then authorize with your Beamtrace account when prompted.
- Run
codex mcp add beamtrace --urlwith the URL below (or seturlunder[mcp_servers.beamtrace]in~/.codex/config.toml). - Run
codex mcp login beamtraceif the server needs OAuth. - In a Codex session, run
/mcpto verify the server is connected.
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 Codex CLI setup that allows custom MCP / connector tools.
