Relve

    Relve MCP Server

    @relvehq/mcp-server

    Install on npm
    v1.0.0 · Beta
    developer-tools
    mcp
    ai-tools
    claude
    anthropic
    cursor
    agents

    The Relve MCP server gives Claude Code, Claude Desktop, Cursor, Continue, and any MCP-compatible client direct access to Relve's AI tools catalog, curated events, funding signals, and strategy frameworks — without opening a browser. One config block, no env vars.

    Quick install

    Terminal
    npx -y @relvehq/mcp-server

    Boots the stdio server locally — same one your agent spawns.

    Overview

    What is the Relve MCP?

    Relve MCP is a Model Context Protocol server that connects Relve's AI-tools intelligence platform to any MCP-compatible client. It exposes 14 typed tools — catalog search, side-by-side comparisons, integration lookups, events, funding signals, and strategy frameworks — so an agent can answer market-intel questions without browsing the web.

    Key features

    • One config block. No clone, no build, no env vars, no API keys.
    • 14 typed tools across discovery, reverse lookups, events, funding, and strategy analytics. Your agent picks the right one.
    • Backed by Relve's public HTTPS API at relvehq.com/api/mcp. Edge-cached so most calls land in under 100ms.
    • Standard MCP stdio transport. Works in Claude Code, Claude Desktop, Cursor, Continue, and anything that speaks MCP.
    • Open source (MIT). Auditable, contributable, free for any use.

    Use cases

    • Pull live tool catalog data into a coding agent without scraping the public site.
    • Compare 2 to 5 AI tools on pricing, integrations, or AI-SEO authenticity from a chat prompt.
    • Surface upcoming AI events and recent funding rounds inside research workflows.
    • Score a tool's competitive moat or run a BCG matrix on a category from inside the agent.

    Tools

    14 typed RPCs over Relve's public API. Your agent picks the right one based on the question — no manual dispatch.

    Catalog discovery

    6

    • list_categories

      Every Relve category with live tool counts.

    • search_ai_tools

      Filter by query, category, pricing, rating, API support, free plan, max price, platforms.

    • get_tool

      Fetch one tool by slug; pick sections (basic / profile / reviews / investor / ai_workflow).

    • compare_tools

      Side-by-side 2–5 tools, optional dimensions (traffic / seo / quality / features / pricing / integrations).

    • top_in_category

      Top N tools by traffic / growth / rating / composite.

    • tool_alternatives

      Same-category alternatives to a given tool.

    Reverse lookups

    2

    • find_tools_by_feature

      Find tools shipping a specific feature.

    • find_tools_by_integration

      Find tools integrating with a specific partner.

    Events

    2

    • upcoming_events

      Filter by tag, mode, or date window.

    • get_event

      Full event detail by slug.

    Market signals

    1

    • recent_funding_events

      Funding rounds across the catalog within a time window.

    Strategy analytics

    3

    • moat_score

      Competitive-moat score for a tool.

    • bcg_matrix

      BCG matrix by category (stars / cash cows / question marks / dogs).

    • market_entry_scorecard

      Entry-readiness scorecard for a category.

    Setup

    4 steps · ~2 min

    Get the Relve MCP wired into your client end to end. No terminal commands, no env vars. Paste, restart, ask.

    Quickest way · ~30 sec

    Drop this prompt into Claude Code

    The agent edits your config, walks you through the restart, verifies the connection, and self-diagnoses any errors. Zero manual steps.

    Set up the Relve MCP server for me.

1. Open my Claude Code config file (~/.claude.json on macOS/Linux, %USERPROFILE%\.claude.json on Windows). Add this entry inside the mcpServers object:

"relve": { "command": "npx", "args": ["-y", "@relvehq/mcp-server"] }

If the mcpServers block doesn't exist yet, create it. Keep the JSON valid.

2. Tell me to fully quit Claude Code (close from the menu bar / system tray, not just the window) and reopen.

3. When I'm back, confirm relve shows as Connected by running /mcp. Then test it by asking: "Use the Relve MCP to list AI tool categories."

4. If anything errors, the v1.0.2 error message will include code=<X> (e.g. ENOTFOUND, ECONNREFUSED, UND_ERR_CONNECT_TIMEOUT, UNABLE_TO_VERIFY_LEAF_SIGNATURE). Tell me which code came back and help me fix it — corporate proxy, certificate, DNS, or VPN issue.
    Or set it up manually

    1. Open your MCP client's config file

      Pick your client and open the file. Create it if it doesn't exist — the file is just JSON.

      • Claude Code~/.claude.json
      • Claude Desktop (macOS)~/Library/Application Support/Claude/claude_desktop_config.json
      • Claude Desktop (Windows)%APPDATA%\Claude\claude_desktop_config.json
      • Cursor~/.cursor/mcp.json

    2. Paste the config block

      Drop this into the file's mcpServers object. If the file already has other MCP servers, add relve alongside them.

      {
  "mcpServers": {
    "relve": {
      "command": "npx",
      "args": ["-y", "@relvehq/mcp-server"]
    }
  }
}

    3. Restart your client

      Close the client completely and reopen. The first boot takes ~2 seconds while npx fetches the package from npm — every subsequent run uses the cached copy and starts instantly.

    4. Verify the connection and try a prompt

      Confirm relve shows as Connected, then ask your agent something Relve can answer.

      Verify in Claude Code

      /mcp

      Should list relve ✓ Connected.

      Try a first prompt

      “List every AI SEO category Relve tracks.”

      Returns live category counts. If you get a response, you're done.

    Stuck? The MCP server is open source — ping the team with what you're seeing and we'll help.

    Troubleshoot

    The 4 things that usually break first time. Each card has an auto-fix prompt you can paste into Claude Code so the agent applies the fix for you.

    MCP changes not taking effect

    common

    Closing the Claude Code window does NOT restart the MCP server. The process keeps running in the background with the old config.

    Fix: right-click the Claude Code icon in your system tray (bottom-right corner of Windows taskbar, or menu bar on macOS), choose Quit, then reopen the app.

    TLS / certificate error

    SELF_SIGNED_CERT_IN_CHAIN

    Your corporate proxy or antivirus is intercepting HTTPS. Node refuses the swapped cert. Two fixes.

    Quick bypass (most common)

    Add this env block to your .mcp.json (or ~/.claude.json) under the relve server:

    "env": { "NODE_TLS_REJECT_UNAUTHORIZED": "0" }

    Auto-fix prompt for Claude Code

    Paste the prompt into Claude Code. The agent edits the config, walks you through the restart, and re-tests.

    Proper fix (use corporate CA)

    Export your corp root CA to a .pem file, then point Node at it. Cleaner than the bypass:

    "env": { "NODE_EXTRA_CA_CERTS": "C:\\path\\	o\\corp-ca.pem" }

    Connection timeout / refused

    UND_ERR_CONNECT_TIMEOUT

    You're on a corporate network that requires a proxy for outbound HTTPS. Node's fetch ignores system proxy settings by default, so the MCP server needs an explicit HTTPS_PROXY env var.

    "env": { "HTTPS_PROXY": "http://YOUR-CORP-PROXY-HOST:PORT" }

    Auto-fix prompt for Claude Code

    Don't know your corp proxy URL? Ask your IT team. Common formats: http://proxy.company.com:8080 or with auth http://user:pass@proxy:8080.

    Can't reach relvehq.com at all

    ENOTFOUND / EHOSTUNREACH

    Your machine can't resolve or reach relvehq.com at all. Network-level, nothing the MCP can fix.

    Quick test in any terminal:

    curl https://relvehq.com/api/mcp/categories

    If that returns JSON → the network is fine, re-check the config + restart. If that fails too → it's a VPN, firewall, or DNS issue on your machine. Try a phone hotspot to isolate.

    Still stuck? The v1.0.2 error message includes a code=<X> you can paste back to the team so we can map a new failure mode for the next release.

    Examples

    6 prompts

    Real prompts that an agent can answer end-to-end via the Relve MCP. Each one shows the natural-language question, the tool the client picks, and what the response carries back.

    • “List every AI SEO category Relve tracks.”

      list_categoriesEvery Relve category with live tool counts and the top 3 picks per bucket.

    • “Find AI tools that integrate with Notion.”

      find_tools_by_integrationSlug, name, and integration type for every tool with a Notion connector. Ranked by integration depth.

    • “Compare Surfer SEO and Frase on pricing and integrations.”

      compare_toolsSide-by-side matrix on the requested dimensions, with a computed winner per row.

    • “Show me funding events in AI SEO from the last 90 days.”

      recent_funding_eventsDate-sorted funding rounds across the catalog. Round, amount, lead investors, vendor URL.

    • “What's the BCG matrix for AI SEO tools?”

      bcg_matrixStars / cash cows / question marks / dogs with the leaders per quadrant and the metric thresholds used.

    • “Score the moat for surfer-seo.”

      moat_scoreComposite 0-100 moat score with the underlying signals (traffic durability, integration breadth, switching cost).

    FAQ

    Click any question to expand.