# Sponsorbook [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Influship/sponsorbook-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 193  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sponsorbook

## Description
Research YouTube sponsors, inspect sponsorship evidence, and manage brand lists with Sponsorbook.

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

```json
"mcpServers": {
  "sponsorbook": {
    "command": "npx",
    "args": ["-y","@sponsorbook/mcp"]
  }
}
```

## Documentation

## What Sponsorbook MCP server does

Sponsorbook MCP server gives compatible MCP clients access to Sponsorbook’s YouTube sponsorship research service. Agents can search for sponsor brands using criteria such as name, domain, language, recency, sponsorship volume, and typical video views. They can then inspect a brand’s sponsorship history and review the videos and creators associated with those relationships.

The service also supports relationship research. An agent can examine creators sponsored by a brand, identify brands that share creator relationships, search YouTube channels, and see which brands have sponsored a channel. Research can be organized into lists, with brands saved for later review and notes attached to the research.

Contact workflows are included. Agents can view masked contact information, explicitly reveal a stored email, or request a contact when Sponsorbook does not already have one. These actions remain subject to the workspace’s permissions and contact rules.

## How it works

The repository provides an open-source bridge for MCP clients that launch local commands. The research service and catalogue are operated by Sponsorbook’s hosted MCP server rather than by the repository itself. The hosted service applies the same workspace permissions, contact-reveal rules, and catalogue limits as the Sponsorbook web application.

There are two connection patterns. Clients that support authenticated remote MCP can connect to `https://app.sponsorbook.io/mcp`. Clients that launch local MCP processes can run the published package through `npx`. On the first connection, a browser opens for sign-in and workspace selection. Later connections reuse the authorization.

## Setup and configuration

A Sponsorbook Pro workspace is required. For a local installation, use Node.js 20.18.1 or later and configure the client to run `npx -y @sponsorbook/mcp`. Remote-capable clients can use the hosted endpoint instead of launching the local package.

The `SPONSORBOOK_MCP_URL` variable is available when testing another Sponsorbook deployment. It must point to an HTTPS endpoint or an HTTP localhost endpoint for that development scenario; it is not presented as a required variable for normal use.

For repository development, the documented commands are `npm install`, `npm test`, and `npm run test:live`.

## Tools and capabilities

The Sponsorbook MCP server supports these research areas:

- Find sponsor brands by descriptive and performance-related filters.
- Review sponsorship history with supporting video evidence.
- Explore sponsored creators and overlapping brand relationships.
- Search YouTube channels and inspect their sponsor history.
- Create research lists, save brands, and add notes.
- View masked contacts, reveal stored emails, or request missing contacts.

## Limitations and notes

Access depends on a Sponsorbook Pro workspace and its authorization. Contact visibility and reveal actions are governed by workspace permissions and Sponsorbook’s contact rules. Catalogue limits also apply through the hosted service.

The local package is a bridge, not a separate copy of the Sponsorbook catalogue. Choosing the remote endpoint requires a client that supports remote MCP with authentication, while local use requires a client capable of launching MCP commands and a supported Node.js version. The repository is licensed under MIT.

The repository includes a private vulnerability-reporting path through GitHub for security issues.

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