# Seovendor [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://seovendor.co/api/mcp  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/seovendor

## Description
A FastMCP server that exposes SV's SEO and GEO tools natively to AI agents — Claude Desktop, Claude Code, Cursor, and any MCP-capable host. Built directly on the sv-cli core library: no duplicated resolver, auth, or async-task logic.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "seovendor": {
    "url": "https://seovendor.co/api/mcp"
  }
}
```

## Documentation

## What the Seovendor MCP server does

Seovendor MCP server makes SV's SEO and GEO tools available to AI agents through MCP. That lets an MCP-capable host use the listed SV capabilities as agent tools rather than requiring a separate, client-specific implementation.

The available description positions the server for work in SEO and generative engine optimization. It does not provide a detailed catalog of individual tool names, arguments, return values, or supported workflows, so those details should be verified from the service or its current documentation before building against it.

## How it works

The server uses FastMCP as its server framework and is built directly on the sv-cli core library. According to the supplied material, this shared foundation covers resolver, authentication, and asynchronous-task logic. In practice, the MCP host communicates with the server, while the server exposes SV's SEO and GEO capabilities to the agent through MCP.

Using the existing core library means the MCP layer is described as an interface over SV's established command-line functionality rather than a separately duplicated implementation. The available information does not specify the transport, request format beyond MCP, or whether tool execution is synchronous from the client's perspective.

## Setup and configuration

The supplied source is `https://seovendor.co/api/mcp`. The listing does not include installation commands, package requirements, startup arguments, authentication setup, or environment variable names. As a result, configuration cannot be documented reliably from the available material alone.

Clients explicitly named in the listing are Claude Desktop, Claude Code, and Cursor. The description also states that the server can be used with any MCP-capable host, although client-specific setup instructions are not provided here.

## Tools and capabilities

The supported capability areas are:

- SEO tools exposed through MCP
- GEO tools exposed through MCP
- Shared resolver logic from sv-cli
- Shared authentication logic from sv-cli
- Shared asynchronous-task logic from sv-cli

The material does not identify individual operations within the SEO or GEO groups. Developers should check the live service documentation for exact tool schemas and required inputs before wiring agent workflows to them.

## Limitations and notes

The Seovendor MCP server listing is brief and does not include a README. It does not establish a license, required environment variables, installation procedure, transport details, rate limits, response schemas, or a complete tool inventory. Those omissions do not indicate that the features are unavailable; they only mean they cannot be specified accurately from the provided source material.

Reach for Seovendor MCP server when the target agent already supports MCP and the required work falls within SV's SEO or GEO tooling. For production integration, confirm authentication and task-handling behavior, then test the available tools against the current service documentation.

_Full upstream README: https://allmcps.com/mcp/seovendor/readme_