# SiteData MCP [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/SiteData-DEV/sitedata-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sitedata-mcp

## Description
Website traffic, DR growth and payment rankings; manage website and keyword favorites via OAuth.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What SiteData MCP MCP server does

SiteData MCP MCP server exposes selected SiteData account and ranking functions to compatible AI clients. It connects through `https://mcp.sitedata.dev/mcp` and uses browser-based OAuth rather than a user-supplied API key. The authorized account can query traffic-growth, Domain Rating-growth, and payment-traffic rankings, or manage saved websites, keywords, and folders.

Ranking access is restricted to SiteData accounts with an active paid membership. Favorite operations are tied to the account that completes authorization. The service is intended for remote MCP clients; ordinary users do not need to clone the repository, install dependencies, or run a local process.

## How it works

The client registers the remote endpoint as a Streamable HTTP MCP service. During sign-in, the user logs in to SiteData and approves the requested `mcp:invoke` scope in a browser. The client receives the authorization through a local loopback callback, and the resulting access applies to the selected SiteData account. The client does not receive the SiteData password or an API key.

Available tool definitions are loaded from SiteData’s `/api/v1/mcp/catalog` when possible. If that platform catalog is unavailable, the repository’s built-in list can be used; the dynamic catalog remains the authoritative source for current parameters.

## Setup and configuration

Add the endpoint to an MCP client that supports remote MCP and browser OAuth. The service URL is:

`https://mcp.sitedata.dev/mcp`

Use `sitedata` as the connection name if the client requires one. Codex CLI supports adding the URL and starting login with the `mcp:invoke` scope. Claude Code can add it with HTTP transport and user scope, then complete authentication through `/mcp`. Cursor, WorkBuddy, and OpenCode each provide remote MCP configuration paths; OpenCode uses a remote entry in `opencode.json` and can start authentication with `opencode mcp auth sitedata`.

After saving the connection, follow the client’s browser authorization flow. A client may need to be restarted or refreshed before the tools appear. No environment variables are required by the documented remote setup.

## Tools and capabilities

The `sitedata_rankings` tool is read-only and requires a `rankingType` of `traffic_growth`, `domain_rating_growth`, or `payment_traffic`. It supports current and archived periods, historical months in `YYYY-MM` format, new-site filtering, payment gateway codes, response locale, and category or business-related tags. Archived queries require a month, and tag filters require both a tag type and tag code. Results are returned without pagination.

The `sitedata_favorites` tool supports listing, adding, updating, and deleting website or keyword favorites. It also creates, renames, and deletes folders. Parameters can identify a domain, keyword, remark, folder, or favorite ID. Add, update, delete, and folder-management actions change account data, so the requested action and target should be checked before execution.

## Limitations and notes

The ranking tool will not provide results to an account without an active SiteData paid membership; the service returns the membership requirement and subscription information instead. The favorites tool is not read-only: several actions can modify or delete saved data. Dynamic catalog definitions should be preferred when they differ from the bundled tool list.

The connection depends on the selected client’s support for remote Streamable HTTP MCP and browser OAuth. Authorization applies to the SiteData account used during login, so changing accounts requires another authorization flow.

_Full upstream README: https://allmcps.com/mcp/sitedata-mcp/readme_