Official description7 sourcesMCP servers8d ago

elfsight/beamtrace-mcp

Track AI search visibility and

View on GitHub ↗Direct link · no redirect page

Config template (adjust for your client)

claude mcp add beamtrace-mcp -- npx -y beamtrace-mcp

A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.

Star count: 0 ★ · elfsight/beamtrace-mcp · read from the repository page · (checked 2026-10-16 20:00:20)
Source: collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history: first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score: score 703 · 7 sources · mcp

FAQ (answers come from our records)

How do I install it?

We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.

Who is it for?

We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

repository elfsight/beamtrace-mcp；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.

Third-party quality signals

Beamtrace for Cursor

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

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
Tools
| Tool | Purpose |
| --- | --- |
| get_visibility | Overall visibility score and insight |
| list_topics | Topic rollups |
| list_prompts | Prompt-level metrics and coverage gaps |
| list_competitors | Visibility leaderboard |
| list_improvements | 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.
Validate
Pre-commit runs the same check via Lefthook (pnpm exec lefthook install after clone).
Local install (dev)
Reload 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:
That 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).
Local / interactive (install mcp-publisher first):
Pick **cursor** / **mcp registry** / **all**, then **patch** / **minor** / **major**, or pass --version. Cursor only bumps .cursor-plugin/plugin.json. MCP also runs mcp-publisher publish.
Namespace 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.