LLM Pulse

io.github.LLM-PulsePublished by GitHub account LLM-Pulsev1.0.0Updated Oct 24, 2026

AI visibility analytics for brand mentions, citations, sentiment, and GEO reports

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Hosted LLM Pulse MCP server that lets an assistant query AI visibility analytics: brand mentions, citations, sentiment, share of voice and GEO reports.

What you can do
  • Read AI visibility metrics such as mention rate, citation rate and weighted visibility
  • Review brand mentions, citations, sources, sentiments and prompt execution data
  • Compare share of voice and top sources across projects and competitors
  • Access recommendation, GEO Writer, Search Console and AI traffic data where the plan allows
When to use it
Useful when you want an assistant to pull AI search visibility and brand reputation numbers, compare competitors, or draft GEO reporting without leaving the chat. It suits marketing and SEO teams already tracking how AI engines mention their brand.
Requirements
A remote Streamable HTTP endpoint at api.llmpulse.ai, reachable over the network. Authentication is required: either OAuth 2.0 with dynamic client registration, or a Bearer token in the Authorization header from an LLM Pulse API key, which is available on Scale plans and above. An optional local npm wrapper can be run with the LLMPULSE_API_KEY environment variable.
Before you install
The Authorization header carries a secret API key; keep it out of shared configs and logs. Access is tied to a paid Scale plan or higher, and some data sets depend on plan access. The server is hosted, so analytics queries and account data go to LLM Pulse's service.

Installation

In SourceWeft

  1. Open LLM Pulse in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.LLM-Pulse%2Fllmpulse-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "llm-pulse": {
      "type": "http",
      "url": "https://api.llmpulse.ai/api/v1/mcp"
    }
  }
}

README

LLM Pulse MCP Server

LLM Pulse is an AI visibility analytics platform for monitoring brand mentions, citations, sentiment, competitor share of voice, and GEO performance across AI search engines.

This repository contains a small runnable wrapper for the hosted LLM Pulse MCP server. It does not contain the private LLM Pulse application source code.

Hosted MCP Endpoint

text
https://api.llmpulse.ai/api/v1/mcp

Transport: Streamable HTTP

Authentication: Bearer token

The hosted endpoint also supports OAuth 2.0 with automatic discovery and dynamic client registration for compatible clients.

Create an LLM Pulse API key in the app, then send it as:

text
Authorization: Bearer llmpulse_your_key_here

API keys are available on Scale plans and above.

Local MCP Wrapper

Run the wrapper with an API key to expose the hosted LLM Pulse MCP tools through stdio:

bash
npm installLLMPULSE_API_KEY=llmpulse_your_key_here npm start

Without LLMPULSE_API_KEY, the wrapper still starts and exposes a read-only setup/status tool. This lets registries verify that the server starts and responds to MCP introspection without requiring a secret.

Docker

bash
docker build -t llmpulse-mcp .docker run --rm -i -e LLMPULSE_API_KEY=llmpulse_your_key_here llmpulse-mcp

Gemini CLI

Install the extension from GitHub:

bash
gemini extensions install https://github.com/LLM-Pulse/llmpulse-mcp

Gemini CLI connects to the hosted endpoint and opens the LLM Pulse OAuth flow when authentication is required.

GitHub Copilot and VS Code

In VS Code, run Chat: Install Plugin From Source from the Command Palette and enter:

text
https://github.com/LLM-Pulse/llmpulse-mcp

The Agent Plugin registers the hosted LLM Pulse MCP server for GitHub Copilot and uses its OAuth sign-in flow.

Kiro Power and Agent Plugin

This repository is also a portable Agent Plugin. In Kiro, choose Powers → Add Custom Power → Import power from GitHub and enter:

text
https://github.com/LLM-Pulse/llmpulse-mcp

Kiro connects to the hosted server and handles the OAuth sign-in flow.

What It Provides

  • Project and competitor dimensions
  • AI visibility, mention rate, citation rate, and weighted visibility metrics
  • Brand mentions, citations, sources, sentiments, and prompt execution data
  • Share of voice and top source analytics
  • Recommendation, GEO Writer, Search Console, and AI traffic data where plan access allows

Documentation

Example MCP Client Configuration

json
{  "mcpServers": {    "llm-pulse": {      "type": "streamable-http",      "url": "https://api.llmpulse.ai/api/v1/mcp",      "headers": {        "Authorization": "Bearer llmpulse_your_key_here"      }    }  }}

Support

Questions? Contact [email protected].

Source: README.md at commit 1d9b938

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts