Skip to main content
Glama

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 — no npm stub).

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: SEO Insights MCP Server

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

Validate

pnpm validate

Pre-commit runs the same check via Lefthook (pnpm exec lefthook install after clone).

Local install (dev)

ln -sf "$(pwd)" ~/.cursor/plugins/local/beamtrace

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:

node scripts/publish.mjs --target all --version "$GITHUB_REF_NAME" --yes

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).

git tag v1.0.1
git push origin v1.0.1

Local / interactive (install mcp-publisher first):

pnpm release

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.

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 --yes

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.

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

No tool schema history has been recorded yet.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    C
    quality
    D
    maintenance
    Connects AI assistants to SE Ranking's SEO and project management APIs to enable natural language queries for keyword research, backlink analysis, and technical audits. It supports comprehensive tasks including competitive analysis, domain traffic tracking, and AI search visibility monitoring.
    100
    Apache 2.0
  • A
    license
    Not graded
    quality
    F
    maintenance
    Connects AI assistants to SEO APIs for backlinks analysis, keyword research, and traffic analysis.
    16
    28
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Connects AI assistants to Google Search Console data for SEO analysis, including search analytics, URL inspection, sitemaps, indexing, and opportunity detection.
    17
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    Connects Tracora brand and query data to MCP assistants, enabling listing of active brands and AI visibility queries via two read-only tools.
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elfsight/beamtrace-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server