Beamtrace
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Beamtrace what's our visibility score and what content improvements do you recommend?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Beamtrace for Cursor
Cursor plugin that connects to Beamtrace's remote MCP for read-only AI visibility insights.
Also includes server.json for the MCP Registry (remote-only) and a stdio introspection shim for catalog Docker builds.
What's included
MCP:
https://beamtrace.com/api/mcp(OAuth; organization's website is resolved automatically)Rule: how to interpret metrics and phrase human reports
Related MCP server: Google Search Console MCP Server
Tools
Tool | Purpose |
| Overall visibility score and insight |
| Topic rollups |
| Prompt-level metrics and coverage gaps |
| Visibility leaderboard |
| Prioritized content improvements |
Stdio catalog image
The product MCP is remote (https://beamtrace.com/api/mcp). This repo also ships a stdio shim that lists the same five tools so a Docker image can start and answer introspection (initialize / tools/list). The shim does not call Beamtrace APIs.
docker build -t beamtrace-mcp .
docker run -i --rm beamtrace-mcpValidate
pnpm validatePre-commit runs the same check via Lefthook (pnpm exec lefthook install after clone).
Local install (dev)
ln -sf "$(pwd)" ~/.cursor/plugins/local/beamtraceReload Cursor → Customize → confirm Beamtrace loads → authenticate MCP.
Release
Pushing a v* tag (for example v1.0.1) runs .github/workflows/publish-mcp.yml. It logs in with HTTP domain auth, then:
node scripts/publish.mjs --target all --version "$GITHUB_REF_NAME" --yesThat sets .cursor-plugin/plugin.json and server.json to the tag version (v prefix is stripped), publishes to the MCP Registry, then commits those files to the default branch if they changed. The tag itself stays on the original commit.
Add repository secret MCP_PRIVATE_KEY: the 64-character hex private key used with mcp-publisher login http (not the PEM file).
git tag v1.0.1
git push origin v1.0.1Local / interactive (install mcp-publisher first):
pnpm releasePick cursor / mcp registry / all, then patch / minor / major, or pass --version. Cursor only bumps .cursor-plugin/plugin.json. MCP also runs mcp-publisher publish.
pnpm release -- --target cursor --bump patch --yes
pnpm release -- --target mcp --bump minor --yes
pnpm release -- --target all --bump patch --yes
pnpm release -- --target all --version 1.0.1 --yesNamespace com.beamtrace/mcp needs domain auth for beamtrace.com (docs). Local login: pnpm registry:login:http. Use pnpm registry:login:github only for GitHub-owned namespaces.
Keep server.json version aligned with the live MCP serverInfo.version when you publish.
Auth
After install, complete Beamtrace sign-in when Cursor prompts. You need a Beamtrace account with a website at beamtrace.com/setup.
Publisher: Elfsight.
Available Tools
5 toolsget_visibilityGet AI visibility scoreARead-onlyIdempotent
Get overall AI visibility for the account website: visibility score (0–100), delta vs previousPeriod, and a short insight. Use this for a high-level snapshot before drilling into topics, prompts, or competitors. When no website is set up for the account, returns setup guidance pointing to https://beamtrace.com/setup and an empty structured payload (null period/metrics or empty lists) — follow server instructions; do not invent dates or scores.
Inputs: no named parameters. Returns: period, insight, previousPeriod, visibilityScore, +1 more
list_competitorsList competitor leaderboardARead-onlyIdempotent
List the visibility leaderboard for the account website with share-of-voice metrics. Returns up to 8 rows including the owned website for comparison. If the owned website sits outside that window, it and the brand just ahead are appended — so list order is not always strict score order. Prefer visibilityRank (then share of voice) when comparing. Highlight isKeyCompetitor rivals when comparing. When no website is set up for the account, returns setup guidance pointing to https://beamtrace.com/setup and an empty structured payload (null period/metrics or empty lists) — follow server instructions; do not invent dates or scores.
Inputs: no named parameters. Returns: period, competitors, previousPeriod
list_improvementsList content improvementsARead-onlyIdempotent
List content improvements for the account website, already ordered by product priority. Includes open and completed items (status: todo, help_requested, review, done) with impact and effort. Prefer open items unless the user asks for completed work. An empty list means no improvements are available yet (or metrics/actions are still being collected). When the user asks what to improve, lead with these product recommendations before any extra strategy. When writing for humans, spell out enum labels (e.g. very_high → 'very high', help_requested → 'help requested'). When no website is set up for the account, returns setup guidance pointing to https://beamtrace.com/setup and an empty structured payload (null period/metrics or empty lists) — follow server instructions; do not invent dates or scores.
Inputs: no named parameters. Returns: improvements
list_promptsList promptsARead-onlyIdempotent
List tracked prompts for the account website with visibility metrics, parent topicId, mentioned flag, and per-prompt competitors (ranks 1–10). Prefer after list_topics when you need specific query-level detail. Rows with mentioned false are coverage gaps. When naming a prompt's topic, match topicId to list_topics and use that topic's name exactly. Counts of gaps vs total must use the returned prompts array length (not list_topics[].promptCount). When no website is set up for the account, returns setup guidance pointing to https://beamtrace.com/setup and an empty structured payload (null period/metrics or empty lists) — follow server instructions; do not invent dates or scores.
Inputs: no named parameters. Returns: period, prompts, previousPeriod
list_topicsList topicsARead-onlyIdempotent
List topic rollups for the account website with visibility score, share of voice, ranks, deltas, and per-topic competitors (ranks 1–10). List order is not importance order — sort yourself when ranking opportunities. promptCount is the topic's prompt total and may exceed how many rows list_prompts returns for that topic. Use list_prompts when you need per-prompt detail or coverage-gap counts. When no website is set up for the account, returns setup guidance pointing to https://beamtrace.com/setup and an empty structured payload (null period/metrics or empty lists) — follow server instructions; do not invent dates or scores.
Inputs: no named parameters. Returns: period, topics, previousPeriod
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct aspect: overall visibility, topic rollups, prompt-level details, competitor leaderboard, and improvement recommendations. The boundaries are clear and unlikely to cause confusion.
Names follow a clear verb_noun pattern, mostly using list_ for collection-style tools. get_visibility is the only get_ exception, but it is still consistent and readable.
Five tools is well-scoped for an analytics-focused server, covering the primary data views without unnecessary bloat or missing core functionality.
The tool set covers the full read-only analytics journey: high-level snapshot, topic rollups, prompt details, competitor comparison, and actionable improvements. Setup guidance is handled via returned messages, so no obvious gaps remain.
Maintenance
Related MCP Connectors
Connect AI agents to your AI visibility and SEO data: competitors, citations, GSC, GA4, Bing.
AI visibility for brands and agencies: scores, rankings, prompts, source gaps, evidence. OAuth.
Read-only Google Search Console and Google Analytics for AI agents.
AI Visibility Isn’t Luck. It’s Signal Alignment. Read-only MCP access to Market Brew, a patented search engineering platform for SEO and AI visibility. Market Brew uses particle swarm optimization and template models to reverse engineer observed search behavior. Inspect ranking models, content alignment, knowledge bases, crawl data, and AI visibility history through a hosted Streamable HTTP MCP server. Requires an enabled Market Brew account and OAuth. Setup guide: https://brew.marketbrew.ai/customer-manual.htm#api-and-chatgpt-read-access
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to SEO APIs for backlinks analysis, keyword research, and traffic analysis.6 npm28MIT
- AlicenseAqualityDmaintenanceConnects AI assistants to Google Search Console data for SEO analysis, including search analytics, URL inspection, sitemaps, indexing, and opportunity detection.17MIT
- FlicenseNot gradedqualityDmaintenanceConnects Tracora brand and query data to MCP assistants, enabling listing of active brands and AI visibility queries via two read-only tools.-
- AlicenseAqualityBmaintenanceMCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection21108 npm1MIT