Overview
Agents inspect visibility and the improvement backlog before opening content tasks.
What you can do
These are the jobs the integration is built for.
Inspect visibility before Factory opens tasks
Factory agents can read Beamtrace metrics and the improvement backlog before creating or executing content work. Tasks start with prompt-level context about who you are losing to and why.
Run a metric-backed content sprint
Ask Droid to sequence edits across pages that map to losing prompts, checking Beamtrace between steps. Long agent runs stay aligned with visibility goals instead of drifting to low-impact files.
Combine Beamtrace with other MCP tools
Factory workflows can fetch visibility from Beamtrace, then hand results to ticketing, design, or docs MCP servers in the same run. Each tool sees the same snapshot of scores and gaps.
Set up
Connect Factory to the shared Beamtrace MCP endpoint, then authorize with your Beamtrace account when prompted.
- In Droid, run
droid mcp add beamtracewith--type httpand paste the URL below (or type/mcpand add the server). - Run
/mcpand complete browser sign-in if authentication is required. - Confirm status with
droid mcp list.
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 Factory setup that allows custom MCP / connector tools.
