# Rivalize [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/Downshift/rivalize-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 1032  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/rivalize

## Description
Competitive intelligence for agents: competitor teardowns, pricing, ads, reviews and momentum.

## Tools
Capabilities this server exposes over MCP:

- **teardown_competitor** — One-call strategy teardown of a competitor as Markdown: positioning, pricing, ads, social, reviews, hiring, momentum and weaknesses to attack, with when the data was last refreshed
- **list_universe_companies** — Search the Rivalize universe, the cross-customer dataset of tracked companies
- **get_universe_company** — Full universe profile for one company: identity, pricing, features, ads, social, reviews, funding and hiring, rankings, signals, momentum
- **list_projects** — The projects in your account; returns the `project_id` other tools take
- **list_reports** — Your reports, newest first. Reading never generates a report
- **get_report** — One report as Markdown, whole or one section or one competitor at a time
- **list_competitors** — The competitors you track, with momentum score, its threat-level band and, where the API provides it, each rival's standing on your Brief
- **get_competitor_intelligence** — Latest stored intelligence for one tracked competitor; a field is present only when it was measured
- **get_battlecard** — Cited sales battlecard for one tracked competitor. Requires a Pro plan
- **get_strategic_timeline** — Evidence-linked timeline of competitor moves across pricing, product, people, funding and content/social
- **get_competitive_landscape** — Current or stored weekly positions of competitors by activity and strategic importance
- **get_freshness** — When each tracked competitor in a project was last actually observed, and how
- **get_evidence** — The sources behind the facts for your product or one competitor: URL, what it supports, and when it was read
- **add_competitor** — Add competitor URLs to a project. Spends credits and queues analysis
- **run_report** — Starts a real report that uses your credits** (paid dashboard plans; about 10 to 20 minutes). Two steps: without `confirm` it starts nothing and returns a preview (depth, the project's competitors, the credits it will use, credits and monthly reports left, expected time). With `confirm: true` it st…
- **get_report_status** — Whether a report started with `run_report` has finished (`processing`, `completed`, `no_competitors`, `no_rivals`), and the next call. Poll no more often than every 30 seconds
- **list_agent_competitors** — Agent plans.** The 3 tracked-competitor slots: who is tracked, when each was last collected, when it refreshes next (every 7 days), and how many slot changes are left this calendar month
- **get_agent_competitor** — Agent plans.** The raw data collected about one tracked competitor, by group (`core`, `ads_seo`, `extended`), each module with its source and `collected_at`. A group your plan does not include is listed under `not_in_plan`. Your own assistant does the analysis
- **set_agent_competitor** — Agent plans.** Put a competitor in a slot, or replace the one in a slot (`slot` 0-2). Uses no credits and queues a collection. Each slot can be replaced once per calendar month (the refusal gives the reset date); a fourth competitor at once is refused

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

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

**Requires environment variables:** `RIVALIZE_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Rivalize does

Rivalize MCP server gives an MCP-compatible assistant access to Rivalize competitive intelligence. It covers competitor positioning, pricing, features, advertising, SEO and social activity, reviews, funding, hiring, rankings, signals, and momentum. Results include collection or refresh dates and, where available, source URLs and the facts those sources support.

The server can work with two kinds of Rivalize data. Account tools expose projects, tracked competitors, reports, strategic timelines, competitive landscapes, freshness details, evidence, and cited battlecards. Universe tools search Rivalize's cross-customer collection of companies and retrieve a profile for a selected domain. The service also supports an Agent plan workflow in which Rivalize collects raw competitor data and the connected assistant performs the analysis.

## How it works

The package runs as an MCP process over stdin and stdout. Configure an MCP client to launch `npx -y @rivalize/mcp`, then provide a Rivalize API key. Account-oriented calls generally use a project ID, report ID, or competitor ID obtained from an earlier listing call; domain-based tools can inspect a company directly.

Most operations read stored intelligence. `run_report` is different: it can start a paid report that consumes credits and typically takes about 10 to 20 minutes. It first returns a preview unless confirmation is supplied, after which `get_report_status` can be used to check progress. Report polling should be no more frequent than every 30 seconds.

## Setup and configuration

Node.js 22 or newer is required. Create an API key in Rivalize under Settings → API Keys; keys begin with `rk_live_`. Set it as `RIVALIZE_API_KEY` in the MCP client's environment.

Claude Desktop, Cursor, and Cline use a stdio server entry with `npx` and the `@rivalize/mcp` package. Claude Code can add the same server from its command line. On Windows, clients that cannot launch `npx` directly can use `cmd` with `/c npx -y @rivalize/mcp`.

The optional `RIVALIZE_MCP_ALLOW_WRITES` setting enables write tools when set to `1`, `true`, or `yes`. Without it, those tools are not registered with the client.

## Tools and capabilities

- Produce a one-call Markdown teardown covering positioning, pricing, ads, social activity, reviews, hiring, momentum, and weaknesses.
- Search the Rivalize company universe or retrieve a full company profile.
- List projects and tracked competitors, including momentum and threat information where available.
- Read reports in full, by section, or by competitor without generating a new report.
- Retrieve cited battlecards, evidence records, freshness data, strategic timelines, and competitive landscapes.
- Add competitor URLs, start reports, and manage Agent-plan competitor slots when write access is enabled.
- Inspect Agent-plan raw collection groups with their sources and collection timestamps.

## Limitations and notes

Plan capabilities affect what the server can return. Battlecards require Pro, while report execution is for paid dashboard plans and uses credits. The Agent plan tracks three competitors at once, refreshes them every seven days, and permits one change per slot per calendar month. Its documented allowance is 500 API and MCP calls per day, with a 250-per-hour limit.

Write operations have side effects: adding competitors queues analysis, report runs spend credits, and changing Agent-plan slots queues a collection. The server does not perform analysis for the Agent plan; it supplies Rivalize's collected JSON and sources for the connected assistant to interpret.

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