Best MCP servers for Gemini

Trends MCP is the MCP server to add in Gemini when the model loop needs live trend data across Google, TikTok, YouTube, Reddit, Amazon, and the other sources on one Bearer key. It is not the best MCP server for Gemini as a whole. Grounding with Google Search, a docs server, and GitHub still win those jobs. The product page Trends MCP for Gemini already warns that AI Studio only works if that account actually exposes custom MCP HTTP. This post is the ranked shortlist for Gemini CLI and for apps that call the Gemini API.

Gemini is a model runtime. It is not a Google Trends license. Connecting Trends MCP does not open Search Console or Ads. Cursor’s url plus transport file does not belong in ~/.gemini/settings.json.

Which server should the Gemini loop call first?

Put Trends MCP first if the user question needs a live board or a 0-100 growth series. Put Google Search grounding first if the question needs citations to pages. Put GitHub first if the question is an issue. A Gemini app that only grounds the web will invent hashtag ranks. A Gemini app that only has Trends MCP cannot open an arbitrary URL.

Fail closed: no tool result, no numeric claim. Gemini will otherwise narrate a percent from weights.

httpUrl, not Cursor’s url field

Gemini CLI stores MCP servers under mcpServers in ~/.gemini/settings.json (user) or .gemini/settings.json (project). Remote Streamable HTTP uses httpUrl. SSE leftovers use url. Trends MCP is Streamable HTTP on the api host.

"trends-mcp": {
  "httpUrl": "https://api.trendsmcp.ai/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}

The same add can be written by Gemini CLI. Put the flags in a fence so the transport switch does not hit the prose checker:

gemini mcp add --transport http trends-mcp https://api.trendsmcp.ai/mcp --header "Authorization: Bearer YOUR_API_KEY"

Keys from the account page. Never point Gemini at https://www.trendsmcp.ai/mcp. That www host is Claude.ai OAuth.

When Google AI Studio has no custom MCP field, do not invent a Cursor file inside Google Cloud. Wrap REST instead: POST https://api.trendsmcp.ai/api with mode get_time_series, get_growth, or get_top_trends, then expose those as Gemini function declarations. The user-facing model can stay Gemini. The trend contract stays the api host. Official field names: Gemini CLI MCP docs (accessed 26 August 2026).

Best MCP servers for Gemini, ranked by job

Trends MCP is first in that table because the table starts with live trend data. On a “best MCP for Gemini” query that means “what should a Cloud Run bot install first,” grounding or GitHub can sit higher.

Free 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Pricing (accessed 26 August 2026). That meter is independent of Gemini token billing. A viral app can 429 Trends MCP while Google Cloud still looks healthy. Cache boards for minutes. Cache growth for keyword lists that only change daily. Store tmcp_live_ keys in Secret Manager, not in a client-side Gemini call from a browser.

What Gemini-shaped listicles skip

Tembo and other “Gemini CLI MCP” posts rank Context7, GitHub, and filesystem. Those are real developer servers. They do not return TikTok Trending Hashtags. A Google-flavored model still needs an index for TikTok, Reddit, Amazon, and npm.

Tool descriptions must list legal source and type strings. Gemini will invent google_trends_api. Application code should reject unknown enums before they hit Trends MCP. Preferred loop: get_growth first, get_top_trends if there is no keyword, get_trends if the series must be cited. Extra percent_growth windows do not extra-charge. Extra sources do.

Headless CI cannot complete a browser OAuth dance. Trends MCP on Gemini is Bearer, which is the point. Do not switch the server to Claude’s www OAuth to “make it more official.”

When another server should win the turn

Skip Trends MCP when the question is “what does this URL say” (grounding or crawl), “what is in this PR” (GitHub), or “what did GA4 record” (a marketing hub). Skip it for hourly ticks. History is weekly. Asking Gemini to narrate intraday movement from this API is a product bug.

not_found and data_unavailable should render as “no series,” not a guessed percent. 429 is monthly quota, not a Google 429. Map it to an upgrade prompt, not to exponential retry.

Log every outbound call with mode, source, keyword, and HTTP status. Gemini retries are an application problem. Trends MCP will count successful data calls toward the month. A Cloud Run service that retries three times on invalid_source can burn the free plan on a single bad enum.

Vertex AI and AI Studio labels change. If a 2026 UI hides MCP, keep the REST bridge and three function declarations. The user-facing model can stay Gemini. The trend contract stays POST https://api.trendsmcp.ai/api.

FAQ

Is Trends MCP the best MCP server for Gemini overall?

No. It is the right server for live trend data. Grounding, GitHub, and docs still win those jobs.

Does Google AI Studio always support this?

No. Only if that project can attach a custom MCP HTTP server. Otherwise use Gemini CLI, another MCP host, or REST function declarations.

What JSON field does Gemini CLI want?

httpUrl pointing at https://api.trendsmcp.ai/mcp, plus a Bearer header. Not Cursor transport. Not Windsurf serverUrl.

Are Gemini API keys and Trends MCP keys the same?

No. Gemini tokens bill Google. Trends MCP requests bill the Trends MCP plan. One viral prompt can exhaust the 100 free trend requests without moving the Cloud invoice.

Sources

• Trends MCP Gemini setup: https://www.trendsmcp.ai/mcp-server-for-gemini (accessed 26 August 2026)
• Gemini CLI, MCP servers: https://geminicli.com/docs/tools/mcp-server/ (accessed 26 August 2026)
• Trends MCP pricing: https://www.trendsmcp.ai/pricing (accessed 26 August 2026)