Getting started/Connect to Claude, or use the API

Connect to Claude, or use the API

Connect FYPNow to Claude in about thirty seconds, call the REST API directly, or point any MCP client at the same tools. Needs an active paid plan.

Updated Sep 9, 2026·3 min read

FYPNow's video analysis, creator tracking and viral trend discovery are available outside the dashboard too: a REST API under https://api.fypnow.com/v1, and the same surface again as an MCP server at https://api.fypnow.com/mcp so an AI assistant can call it as tools. Claude connects over OAuth with no API key at all — you approve it once and pick which workspace it acts on. Other MCP clients (Cursor, VS Code, Windsurf) and direct REST calls use a bearer key.

The API and MCP server cover TikTok only for now. YouTube Shorts analysis is available in the web app — paste a Shorts link into Analyze video — but not yet through analyze_tiktok_video or POST /v1/analyses, which reject YouTube links.

Connect from Claude

No API key needed — Claude uses OAuth, so you approve the connection in the browser and choose which workspace it acts on.

In Claude, open Settings → Connectors and choose Add custom connector.
Enter https://api.fypnow.com/mcp as the URL. Leave authentication blank — Claude discovers it.
A FYPNow window opens. Pick the workspace the connection should act on, choose Read and write or Read only, and approve.
Claude lists the tools automatically. See MCP tool reference for the full set and what each one costs.

A connection acts on exactly one workspace, chosen at approval. Only workspaces on an active paid plan can be selected. To use a different one, connect again and pick it.

For everything else: an API key

Cursor, VS Code, Windsurf, direct REST calls and your own scripts use a bearer key instead. Go to Settings → API (workspace admins only) and create one — name it, choose read or read+write, and copy it immediately: it is shown exactly once. API and MCP access require the workspace to be on an active paid plan (a free trial counts); see Plans & limits.

Reads — browsing, checking usage, looking up what's already analyzed — cost nothing beyond the request itself. Only analyzing a video, creating a Viral Content Agent, searching trends and generating a script draw down a plan quota. See Rate limits & quotas for exactly which.

Settings → API has a ready-to-copy MCP config block for bearer-key clients.

Connect from ChatGPT

The OAuth flow Claude uses is the same one ChatGPT's app directory requires, and it is live. FYPNow is not yet listed in that directory, so there is no one-click install; a ChatGPT custom action can reach the REST API today by sending a bearer key as a plain Authorization header on the endpoints below.

Calling the REST API directly

No MCP client required — every endpoint under /v1 accepts the same bearer key as a normal HTTP Authorization header. See REST reference for the full endpoint list and response shape, or browse the full OpenAPI reference for every parameter and error response per operation. A generated OpenAPI 3.1 document is published at https://api.fypnow.com/openapi.json for typed client generation.

Where to next

Authentication — OAuth, bearer keys, and the one-org-per-credential rule.
MCP tool reference — all 18 tools and their quotas.
REST reference — every endpoint, the envelope, pagination, error codes.
API reference (OpenAPI) — the same endpoints, rendered per-operation from the generated spec.
Rate limits & quotas — including the standing catalog cap that never resets.
Data coverage — the honest numbers on analysis success and gaps.

Was this page helpful?

← Previous

Track a creator

Hook score