TrendsFast

npx add-mcp 'https://trendsfast.com/api/mcp/v3'

Trend research, in your agent.

Connect to /api/mcp/v3 for Global, Niche, Discover and Ask queries over retained evidence. Use confirmed Product DNA when it helps, then inspect sources, dates and limitations. Claude Code, Codex, Cursor and other clients use a scoped key; ChatGPT uses OAuth sign-in and consent for one project, and its directory publication is still pending.

V3 · STREAMABLE HTTP

7 scoped tools. One project.

https://trendsfast.com/api/mcp/v3

Global, Niche, Discover and Ask queries share your credit balance and need an explicit credit limit. Reading Product DNA, balance and saved results is free. No automatic research, purchases, publishing or scheduling.

Global, Niche, Discover and Ask, with a clear credit limit

The V3 endpoint is https://trendsfast.com/api/mcp/v3. It queries retained evidence and returns source dates, coverage and uncertainty. If V3 is not enabled on a deployment, the endpoint answers 404 rather than starting anything.

Any MCP client or directory can initialize and list the tools without a key. Calling a tool always needs authorization: without it the endpoint answers 401 with a WWW-Authenticate challenge and runs nothing.

ChatGPT connects through OAuth sign-in and consent for an owned workspace, and Claude signs in the same way where OAuth is enabled. Do not paste API keys into ChatGPT or configure the protected endpoint as anonymous. Other compatible clients may use an active project-scoped key in protected authorization settings; create one in API keys, which then shows the exact setup for each client. Read the ChatGPT connection guide for the OAuth path.

• trendsfast_discover_trends: at most 5 credits, needs trends:query. One question across global, core and adjacent scope and every channel.
• trendsfast_global_trends: at most 1 credit, needs trends:query. What is trending across the shared index. No brand context needed.
• trendsfast_niche_trends: at most 35 credits, needs trends:query. Trends ranked against your niche. Name a product to collect your brand's sources fresh first.
• trendsfast_ask_trends: at most 5 credits, needs trends:query. One bounded question, answered from saved evidence.
• trendsfast_read_result: free, needs trends:read. Reread or page through a saved result, or recover a lost response.
• trendsfast_project_context: free, needs trends:read. The connected brand and its confirmed niche context.
• trendsfast_credit_balance: free, needs credits:read. The credit balance shared by the dashboard, REST and MCP.

Read tools use trends:read or credits:read. New queries require trends:query, a caller-retained UUID request_id and an explicit max_credits. They are chargeable operations, even though they read a saved index. Empty results cost zero. Only a Niche call that names a product collects that brand's own sources fresh, within its price; no other V3 query dispatches providers or models. After an uncertain response, recover the original request instead of creating another UUID.

Keep OAuth tokens and API keys in your client’s secure credential storage, never in URLs or prompts. Authorization, source permissions, context and retention are checked again on reads. Tool discovery does not prove live source coverage or authorize spending. See the shared V3 response contract, or make the same queries over REST with the curl quickstart.

Connect once. Ask what is trending.

Account → scoped key → MCP or REST → one bounded query → free rereads.

1. Create your free account. A verified account receives 100 free credits once. Global questions need no brand context; adding your brand lets niche queries rank evidence against it.
2. Create a key in API keys. It is shown once and is scoped to one workspace with trends:query, trends:read and credits:read. Keep it in TRENDSFAST_API_KEY in your client’s environment, never in chat, URLs or command arguments.
3. Add the remote MCP server https://trendsfast.com/api/mcp/v3 with that key as a bearer token, or call REST under /v3/trends. Both share one service, one set of scopes and one credit balance.
4. Ask one bounded question. Every query carries a request_id UUID you keep and a max_credits ceiling. A Global query costs at most 1 credit, Niche 3 credits, Ask 5 credits. Empty results cost nothing.
5. Reread the saved result as often as you like. Reads, pagination and recovering a lost response by its request_id cost 0 credits and never start new research.

Tool	Cost	What it does
trendsfast_discover_trends	5 credits	One question across global, core and adjacent scope and every channel.
trendsfast_global_trends	1 credit	What is trending across the shared index. No brand context needed.
trendsfast_niche_trends	35 credits	Trends ranked against your niche. Name a product to collect your brand's sources fresh first.
trendsfast_ask_trends	5 credits	One bounded question, answered from saved evidence.
trendsfast_read_result	free	Reread or page through a saved result, or recover a lost response.
trendsfast_project_context	free	The connected brand and its confirmed niche context.
trendsfast_credit_balance	free	The credit balance shared by the dashboard, REST and MCP.

What does my agent receive?

Trends with their evidence: the original source URL, publication and observation dates, the signal, any measured growth, the platform, and what coverage was and was not available. Ask answers also show how the question was interpreted. Your agent decides what to write or build with it.

Which sources are behind it?

Search, AI search, community and video sources, each with its own status on the sources page. A channel with no permitted observation is reported as unavailable, not as an empty trend list, so “nothing is trending” and “we cannot see there” never look the same.

Which clients work?

Any client that speaks Streamable HTTP MCP with a bearer token: Claude Code, Codex, Cursor and others. ChatGPT connects with OAuth instead of a key. See agent setup for each client’s exact command.

What happens after a lost response?

Keep the same request_id and read /v3/trends/requests/ {request_id} once before deciding anything. A missing response does not mean nothing was debited, and a new identity is a new billable query.

Existing v1 and v2 integrations

/v1, /api/mcp and the Marketing v2 MCP at /api/mcp/v2 are still served for clients built on them, with their own keys and contracts. New connections use V3. See the v1 OpenAPI.

What stays under your control?

Every query is explicit and capped by your max_credits. TrendsFast never posts, schedules or publishes anything; it returns evidence, and you or your agent decide what to do with it.

TRENDSFAST_API_KEY=<your key>   # set in the client's environment
MCP server: https://trendsfast.com/api/mcp/v3

See agent setup, the API reference, Docs and the V3 OpenAPI.

ChatGPT planning connection

A separate public MCP endpoint offers observed trend calculations and contribution planning without a project key. Private briefs and paid generation are outside this connection; directory publication is pending. Read the ChatGPT connection guide.

Existing Marketing v2 keys still connect.

https://trendsfast.com/api/mcp/v2 still answers integrations that hold a Marketing v2 project key in their protected authorization settings, with scopes such as marketing:read and marketing:research. Its tools are named trendsfast_marketing_*_v2, and tool discovery lists the ones the key allows: for example, trendsfast_marketing_intelligence_read_v2 reads saved trend intelligence without provider calls, and trendsfast_marketing_brief_create_v2 creates a brief from the shared research allowance. V3 keys carry no marketing scopes, so they list no tools there; new connections use the V3 endpoint above.

Install one exact agent signal.

The pinned v1 installer adds the public TrendsFast skill and a local stdio bridge to Remote MCP v1. It contains no private research, routing, scoring, prompts, or provider logic.

PRIMARY INSTALL / IMMUTABLE SOURCE

Install the reviewed GitHub release

npx -y github:meestierolff/trendsfast-open#9e7053b47eebfbfdc6ce003edaf7d10b849afc55 install

Requires Node.js 22 or newer. The command is pinned to the accepted public merge; there is no floating branch or unreviewed package alias.

PACKAGE

trendsfast-agent

Version 0.1.0-alpha.0
Binary trendsfast

PUBLICATION

GitHub npx is live

npm status: npm deferred. Use only the reviewed GitHub command above for this release.

CREDENTIAL MODE / ENVIRONMENT ONLY

TRENDSFAST_API_KEY

Export the project-scoped key in the environment before installation. Never place the raw key in argv or client configuration; let the managed MCP process inherit it.

Connect one supported client.

Choose one or more clients in the interactive installer. Other clients must use the generic stdio contract and are not represented as native integrations.

SUPPORTED CLIENT

Generic stdio MCP

For any MCP client that can launch a local stdio command.

Installer selector: --client generic

1. At the prompt, enter generic, or pass --client generic for a non-interactive install.
2. Use the installer-reported config path and let the managed process inherit TRENDSFAST_API_KEY from its environment.

SUPPORTED CLIENT

Claude Code

A tested managed MCP entry and installed TrendsFast skill.

Installer selector: --client claude-code

1. At the prompt, enter claude-code, or pass --client claude-code for a non-interactive install.
2. Restart Claude Code from a shell that already has TRENDSFAST_API_KEY in its environment.

SUPPORTED CLIENT

Codex

A tested managed MCP entry and installed TrendsFast skill.

Installer selector: --client codex

1. At the prompt, enter codex, or pass --client codex for a non-interactive install.
2. Restart Codex from a shell that already has TRENDSFAST_API_KEY in its environment.

Verify before you create.

Doctor and the default demo are read-only. Neither command creates a scan, invokes a provider or model, reserves cost, approves, delivers, publishes, or schedules.

DOCTOR / READ-ONLY

Check the local install and connection

npx -y github:meestierolff/trendsfast-open#9e7053b47eebfbfdc6ce003edaf7d10b849afc55 doctor --json

JSON output reports local configuration, credential availability, contract drift, live source status, and read-only connection health with zero scans created.

DEFAULT DEMO / READ-ONLY

Read existing project evidence

npx -y github:meestierolff/trendsfast-open#9e7053b47eebfbfdc6ce003edaf7d10b849afc55 demo

The default demo reads confirmed project context and the latest existing immutable brief. It creates zero scans and causes zero provider, model, or cost effects.

Create one Customer Demand Brief only on purpose

npx -y github:meestierolff/trendsfast-open#9e7053b47eebfbfdc6ce003edaf7d10b849afc55 demo --create --idempotency-key <uuid-v4> --objective <text> --capability <name>

Template only: replace every angle-bracket field and quote multi-word values before running. Do not paste the template unchanged.

Create requires the explicit --create flag, a caller-created UUID v4 idempotency key, the objective, at least one confirmed content capability, and interactive confirmation.

One confirmed run makes exactly one scan admission. That scan may call configured providers and models and may incur bounded cost. It never approves, delivers, publishes, or schedules the result, and it never retries an ambiguous create.

Troubleshoot without exposing a key.

Start with Doctor. If the managed files drift, remove only the installer-owned entries and reinstall from the same reviewed source.

Node is too old

Install Node.js 22 or newer, then rerun the primary install command.

Key is missing or revoked

Set an active project-scoped key in TRENDSFAST_API_KEY. Never put the key in argv or client configuration.

Install is missing

Run the primary install command above, then run Doctor again.

Managed configuration drift

Do not hand-edit the managed entry. Uninstall it, rerun the reviewed installer, then verify with Doctor.

Client is unsupported

Use Generic stdio MCP, or switch to the tested Claude Code or Codex integrations.

A clean reinstall is needed

Run the immutable uninstall command below, rerun the primary install command, and finish with Doctor.

MANAGED UNINSTALL

npx -y github:meestierolff/trendsfast-open#9e7053b47eebfbfdc6ce003edaf7d10b849afc55 uninstall

Uninstall preserves unrelated client entries. Rerun the primary install command above, then finish with Doctor. Replace a missing or revoked key only through the TRENDSFAST_API_KEY environment variable.

Bring a key and declare the protocol.

Contract trendsfast-remote-mcp-v1. Protocol 2026-07-28. V1 uses direct project-scoped bearer authentication, with next_move:read and next_move:write scopes. Access is feature-gated. Keep an active project key in the Authorization header; never place credentials in a URL or persist them in an MCP session.

POST https://trendsfast.com/api/mcp
Authorization: Bearer <project-scoped-api-key>
Content-Type: application/json
Accept: application/json, text/event-stream
MCP-Protocol-Version: 2026-07-28
Mcp-Method: server/discover

AUTHENTICATION

The key supplies the project

Tool arguments never grant project access. Every resource handle is checked again against the authenticated project on every call.

CLIENT ACCEPT

Advertise JSON and event streams

V1 returns one JSON response, while clients advertise both required media types for Streamable HTTP compatibility.

Six reads. One deliberate write.

Read tools create no scan, provider call, model call, reservation, approval, delivery, publication, or scheduling event.

Tool	Scope	Effect	What it returns
trendsfast_project_context_get	next_move:read	ZERO-EFFECT READ	Return only the authenticated project's current public-safe confirmed context.
trendsfast_today_create	next_move:write	BOUNDED WRITE	Admit one user-intended Customer Demand Brief request with the caller's exact UUID v4 idempotency key; never approve, deliver, publish, schedule, or poll automatically.
trendsfast_today_status_get	next_move:read	ZERO-EFFECT READ	Read the public-safe lifecycle of a known scan owned by the authenticated project.
trendsfast_brief_latest_get	next_move:read	ZERO-EFFECT READ	Return the latest immutable V1 or V2 brief for the authenticated project's current confirmed context.
trendsfast_brief_get	next_move:read	ZERO-EFFECT READ	Return one exact immutable V1 or V2 brief by public brief ID after project ownership is rechecked.
trendsfast_creative_handoff_get	next_move:read	ZERO-EFFECT READ	Return the exact immutable public-safe ShipToUsers creative handoff without calling ShipToUsers, uploading media, creating a generation job, or regenerating content.
trendsfast_sources_get	next_move:read	ZERO-EFFECT READ	Return only the current bounded public source-status projection, including limitations and verification truth.

Read without effects. Create only on purpose.

MCP returns public-safe projections from existing TrendsFast services. It never reads raw provider payloads or turns a handoff into a ShipToUsers network call.

READ-ONLY WORKFLOW / next_move:read

Ground an agent in current evidence

1. Read the confirmed project context.
2. Read the latest or one historical immutable brief.
3. Read its exact creative handoff and current public source limitations.

These calls create no scan, provider or model call, cost reservation, approval, delivery, publication, or scheduling event.

CREATE WORKFLOW / next_move:write

Admit one Today request deliberately

1. Supply the exact intent, objective, and confirmed content capabilities.
2. Generate and send one caller-owned UUID v4 idempotency key.
3. Receive the admission receipt; poll status only when your client chooses.

The server creates no hidden retry key, performs no automatic polling, and never bypasses human review or auto-publishes the result.

The boundaries travel with the result.

Evidence stays visible

Briefs retain their source status, observed evidence, limitations, and honest NO CLEAR TREND semantics. Unsupported momentum is never invented.

Creation stays explicit

Today creation requires the exact intent, current confirmed capabilities, and a caller-created UUID v4 idempotency key. The server never creates a hidden retry.

Human review stays required

TrendsFast recommends. It does not approve, deliver, publish, schedule, manage keys, mutate projects, or expose raw provider data through v1 MCP.