API & MCP/API & MCP: Getting started

API & MCP: Getting started

Call the REST API directly, or connect the MCP server from a bearer-key client such as Cursor, VS Code or Windsurf. Claude and ChatGPT need OAuth, which is not live yet. Both need 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 MCP client can call it as tools. Bearer-key clients such as Cursor, VS Code and Windsurf work today; Claude and ChatGPT require OAuth, which is not live yet.

What you need first

An API key. 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.

Connect from Claude

Create a read+write API key in Settings → API.
In Claude, add fypnow as a custom connector with URL https://api.fypnow.com/mcp and an Authorization: Bearer <your key> header — Settings → API has a ready-to-copy config block.
Claude lists the available tools automatically. See MCP tool reference for the full set and what each one costs.

Connect from ChatGPT

ChatGPT's app directory requires OAuth, not a bearer key (see Authentication) — that connect flow is not live yet. Until it ships, a ChatGPT custom action can still reach the API the same way any HTTP client does: send the bearer key as a plain Authorization header on the REST 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 — bearer keys, OAuth, and the one-org-per-credential rule.
MCP tool reference — all 14 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

Glossary

Authentication