# Seo Ai Visibility [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/pipeworx-io/mcp-seo-ai-visibility  
**GitHub Stars:** 0  
**npm Downloads (last month):** 449  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/seo-ai-visibility

## Description
SEO AI-Visibility MCP — does brand X appear in an LLM's answer (GEO / AI-SEO)

## Tools
Capabilities this server exposes over MCP:

- **seo_llm_answer** — Does `<brand>` appear in ChatGPT's answer for `<question>` — runs a prompt through an LLM and returns its answer plus any cited sources/links, for AI-visibility (GEO) analysis: see what an LLM says about a brand, topic, or query and which sources it cites. Example: seo_llm_answer({ user_prompt: "Wh…

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "seo-ai-visibility": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-seo-ai-visibility"]
  }
}
```

## Documentation

## What Seo Ai Visibility MCP server does

Seo Ai Visibility MCP server helps agents inspect how an LLM responds to questions about a brand, topic, or search-style query. The primary operation, `seo_llm_answer`, accepts a user prompt and an optional model name, sends the prompt through an LLM, and returns the resulting answer together with cited sources or links when available.

This makes the server suitable for AI-visibility, GEO, and AI-SEO checks. For example, an agent can ask which running-shoe brands an LLM recommends, then inspect whether a specific brand appears and which references support the response. The tool reports what the model answered; it does not provide a conventional search-results ranking.

## How it works

The server can be reached through a Pipeworx MCP endpoint or run locally as a package. The scoped gateway URL is `https://gateway.pipeworx.io/seo-ai-visibility/mcp`. That connection lists the SEO tool along with shared Pipeworx gateway tools, including routing and discovery tools. The full gateway is also available when an agent needs direct access to all catalog packs.

The local package uses MCP over standard input and output. In local mode, it exposes only the tools in this pack and does not add the gateway’s shared meta-tools. Both modes use the same source and provide the pack’s core capability.

For HTTP use without an MCP client, the gateway exposes `POST https://gateway.pipeworx.io/v1/tools/seo_llm_answer`. Tool details can be inspected through the corresponding GET endpoint.

## Setup and configuration

Add the gateway URL to an MCP client’s server configuration, or run the standalone package with `npx -y @pipeworx/mcp-seo-ai-visibility`. The local configuration uses the `npx` command and passes the package name as an argument. A gateway connection does not require a local package installation, but HTTP tool calls require a key supplied as `_apiKey`.

The example tool input includes `user_prompt`, `model_name`, and `_apiKey`. The README demonstrates `gpt-4o` as a model value. No environment variables are documented for this server.

## Tools and capabilities

- `seo_llm_answer`: Sends a prompt through an LLM and returns its answer plus cited sources or links.
- Brand and topic visibility checks: Examine whether a brand or subject appears in an answer.
- Gateway access: Use the scoped endpoint or the full Pipeworx gateway.
- Local stdio access: Run the pack without a Pipeworx account or gateway round trip.
- HTTP inspection and invocation: Inspect the tool with GET and call it with POST.

The Seo Ai Visibility MCP server’s central use is comparing an LLM’s response and citations against a visibility question. The result depends on the prompt and selected model.

## Limitations and notes

The gateway pack endpoint includes shared Pipeworx meta-tools in addition to the SEO tool, so its tool list is larger than the pack’s table. The connection’s `initialize` response is the authoritative source for the exact scope at a given time. The local server avoids those shared tools and exposes only this pack’s tools.

Gateway HTTP calls require a private key in `_apiKey`, while the standalone mode is documented as requiring no Pipeworx account. The available README material does not specify supported LLM providers beyond the model example, response guarantees, rate limits, or citation behavior when an answer contains no sources.

_Full upstream README: https://allmcps.com/mcp/seo-ai-visibility/readme_