slope-mcp

MCP server for Slope — proprietary B2B creator-velocity data, straight into any MCP client (Claude Desktop, Cursor, …). Slope banks every tracked video's view curve, so it knows a creator's velocity (views/hour) and whether that velocity is a breakout against the creator's own baseline — the earliest signal that a creator or piece of content is taking off. This data cannot be backfilled from any public source.

{ "mcpServers": { "slope": { "command": "npx", "args": ["-y", "slope-mcp"] } } }

Drop it in your MCP config and your agent gets nine new tools. No signup — the server auto-mints a free API key on first use. Set SLOPE_API_KEY to use your own persistent key.

Tools

| Tool | Input | Returns | |---|---|---| | creator_board | limit?, niche?, sort? | the ranked creator leaderboard — subscribers, crossPlatformReach, velocityViewsPerHour, breakout scores | | creator | slug | one creator's full profile — per-platform accounts, audience growth curve, and recent content with per-video velocity curves | | rising_creators | limit?, niche?, minSubs?, maxSubs? | creators heating up — consistent breakout frequency + intensity over the window (not one-offs) | | breakouts | limit?, confidence? | content breaking out now — relativeScore = current views/hour ÷ the creator's baseline views/hour | | content | videoId | one video + its full first-party velocity curve — viewsPerHour, velocityTrend, peakViewsPerHour, breakout status | | trending_niches | — | niches ranked by breadth (distinct creators surging), with momentum vs the prior window | | cross_platform_rising | limit?, niche?, minSubs?, maxSubs?, sort? | fastest-growing rolled-up audiences across YouTube + captured platforms (followers/hour) | | search_creators | q | creator lookup by name/handle (exact → fuzzy); each hit flags if it's breaking out now | | dataset_summary | — | the whole dataset at a glance — breaking now, hottest niche, biggest audience mover, dataset scale |

Key fields: velocityViewsPerHour / viewsPerHour = current content velocity in views/hour · relativeScore = velocity ÷ the creator's own baseline velocity (a breakout multiple) · subscribers = exact YouTube subscriber count · crossPlatformReach = followers summed across captured platforms · audienceRatePerHour = followers gained per hour.

Example — ask your agent "what B2B creators are breaking out right now?" and it calls breakouts:

{
  "rank": 1,
  "creator": { "name": "Holy Schmidt!", "slug": "holy-schmidt", "handle": "@HolySchmidt", "subscribers": 459000 },
  "relativeScore": 27.64,
  "viewsPerHour": 1382,
  "baselineVph": 50,
  "confidence": "solid"
}

Config

• No signup — the server auto-mints a free key on first call and caches it for the process.
• SLOPE_API_KEY — use your own key (mint one instantly: POST https://yourslope.com/api/v1/keys). Persistent keys keep your rate-limit quota across restarts. Free tier ≈ 600 requests/minute.
• SLOPE_API_URL — override the backend (defaults to https://yourslope.com/api/v1).

Every read is keyed (Authorization: Bearer <key>); the paywall is rate/volume, not data-gating — the same data is available on every tier. Docs: https://yourslope.com/api.

MIT.