Claude.ai OAuth connector for Trends MCP

Claude.ai Pro, Max, and Team plans can attach remote MCP servers through Anthropic's OAuth connector UI. Trends MCP registers as a hosted connector at https://api.trendsmcp.ai/mcp so browser sessions pull live Google, TikTok, Reddit, and Amazon trend data without pasting API keys into JSON.

Claude.ai can call remote Model Context Protocol servers through Anthropic's OAuth connector UI. Trends MCP ships as a hosted HTTPS endpoint at https://api.trendsmcp.ai/mcp. After the connector is saved, browser chat sessions can query normalized trend history, growth windows, and live leaderboards without editing claude_desktop_config.json or exporting API keys into local files.

For Desktop, Code, and multi-client setup, see Trends MCP for Claude. This page covers only the Claude.ai browser connector.

Where to add the connector in Claude.ai

Anthropic places remote MCP under account settings, not inside an individual chat.

  1. Open claude.ai and sign in with a Pro, Max, or Team account.
  2. Open Settings.
  3. Go to Integrations (some builds label the same area Connectors).
  4. Choose Add custom integration or Add custom connector.
  5. Set Name to Trends MCP.
  6. Set Server URL to https://api.trendsmcp.ai/mcp.
  7. Save. Claude runs the OAuth handshake against the hosted server.

After activation, start a new chat and confirm Trends MCP tools appear in the connector list for that workspace. Older chats created before the connector was added may not inherit the tool channel until a fresh conversation is opened.

OAuth connector versus Claude Desktop Bearer token

Client Auth pattern Config location Typical user
Claude.ai browser OAuth through Integrations UI None (cloud) Analysts, PMs, marketers
Claude Desktop Authorization: Bearer in mcpServers JSON claude_desktop_config.json Power users on Mac/Windows
Claude Code claude mcp add with HTTP header Local CLI profile Engineers in terminal workflows

The OAuth path trades local file editing for plan gating. Claude Desktop accepts a free Trends MCP API key (100 requests per month on the free tier) while still requiring a JSON snippet. Browser OAuth skips key paste but needs a paid Claude.ai subscription that enables custom integrations.

Teams often run both: OAuth for stakeholders who live in the browser, Desktop or Code for developers who want keys in shell environment variables. The underlying data contract is identical across clients.

Hosted endpoint and transport details

Field Value
MCP URL https://api.trendsmcp.ai/mcp
Transport HTTP streamable / SSE (remote hosted server)
REST fallback POST https://api.trendsmcp.ai/api with JSON body
API docs https://www.trendsmcp.ai/docs

Remote connectors must use HTTPS. Local stdio wrappers are not required because Trends MCP is already hosted. If a corporate proxy blocks SSE, switch to REST from an automation tool or use Claude Desktop with mcp-remote as documented on the main Claude setup page.

FAQ

Common questions

Paste https://api.trendsmcp.ai/mcp as the server URL when adding a custom integration under Claude.ai Settings. Name the connector Trends MCP. Claude handles OAuth after the URL is saved. The same hosted endpoint works in Claude Desktop, Cursor, and VS Code, but those clients use Bearer token headers instead of the browser OAuth flow.
The OAuth connector path does not require pasting a Bearer token into Claude.ai settings. Authentication is handled through Anthropic's remote MCP handshake. Claude Desktop and Claude Code still need an API key from https://www.trendsmcp.ai/account because they read headers from local config files.
Remote MCP connectors require Claude.ai Pro, Max, or Team. Free Claude.ai accounts cannot add custom integrations. Teams that only use the free tier should run Trends MCP through Claude Desktop with a free API key or call the REST API directly.
Trends MCP exposes get_trends for weekly history, get_growth for preset windows like 3M and YTD, and get_top_trends for live leaderboards such as Google Trends, TikTok Trending Hashtags, and X (Twitter) Trending. Each successful source plus keyword pair counts as one request against the monthly allocation.
The Claude MCP overview covers Desktop JSON, Claude Code CLI, and browser connectors in one place. This page isolates only the Claude.ai OAuth connector path: where to click in Settings, what to paste, how OAuth differs from Bearer tokens, and which prompts reliably trigger tool calls in browser chat.

Explore more

Trends MCP for Claude Connect Trends MCP to Claude Code in minutes Trends MCP for Cursor Google Trends data for AI assistants Every platform, one connection

Ready to plug in?

Start building with live trend data

Free forever for 100 requests per month. No credit card, no setup.

No credit card Instant delivery 100 free requests/mo

By continuing you agree to our Terms & Privacy Policy.

4,090,854 API calls served
Check your inbox Your API key is on its way

Nothing there? Check spam or .

What are you working on?

How will you connect?

Sign in to your account

API key sent to your inbox. Sign in to access your dashboard.