Skip to content

MCP.md

Latest commit

 

History

History
118 lines (77 loc) · 3.43 KB

MCP.md

File metadata and controls

118 lines (77 loc) · 3.43 KB
Raw

MCP Integration — RevidAPI

Connect RevidAPI to Claude Desktop, Cursor, VS Code, Claude Code via Model Context Protocol (MCP).

Status (2026-06): REST API and n8n are live today. MCP server at https://api.revidapi.com/mcp is on the roadmap — configs below are templates using YOUR_API_KEY.

What works today

Method Status Best for
REST / cURL Live Scripts, backends, Make/Zapier
n8n HTTP Request Live Daily automation
Dashboard Marketplace Live Testing endpoints (login required)
MCP server Roadmap Claude Desktop, Cursor native tools

Same endpoints as API Marketplace: base https://api.revidapi.com/paid, header x-api-key.

Option A — REST (recommended now)

No MCP required. Call any endpoint directly:

curl -G "https://api.revidapi.com/paid/tiktok/download" \
  --data-urlencode "url=TIKTOK_URL" \
  -H "x-api-key: YOUR_API_KEY"

Browse all paths: catalog/api-catalog.json · docs.revidapi.com

Option B — n8n

  1. Open n8n.revidapi.com or self-hosted n8n
  2. Add HTTP Request node
  3. URL: https://api.revidapi.com/paid/tiktok/download?url=...
  4. Header: x-api-key = your key (use n8n credentials — not hardcoded in workflow export)

See examples/n8n/http-request.md.

Option C — MCP via mcp-remote (preview / future)

When https://api.revidapi.com/mcp is deployed, use mcp-remote to bridge HTTP → stdio for desktop clients.

Claude Desktop

File: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)

Copy from mcp/claude_desktop_config.json.example:

{
  "mcpServers": {
    "revidapi": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.revidapi.com/mcp"],
      "env": {
        "REVIDAPI_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with your key from dashboard Settings.

Restart Claude Desktop.

Cursor

Project file: .cursor/mcp.json — see mcp/cursor.mcp.json.example.

VS Code

Use MCP extension + same JSON structure as Claude Desktop.

Security checklist

  • Use YOUR_API_KEY in docs; real key only in local config or env
  • Do not commit claude_desktop_config.json with real keys
  • Rotate key if leaked: Dashboard → Settings → revoke & create new
  • AI Studio (ai.revidapi.com) uses a different key — do not mix billing

MCP vs TikHub-style setup

Similar to TikHub MCP:

TikHub RevidAPI
mcp.tikhub.io api.revidapi.com/mcp (roadmap)
API key from user portal revidapi.com/dashboard
755+ endpoints Download, video, media, TTS, search — see catalog
npx mcp-remote Same pattern

Dashboard UI

Live integration hub (copy-paste cURL, n8n snippets):
https://revidapi.com/dashboard/integrations

Support