"Best Gemini MCP server to use with Claude" matching MCP servers:

A Model Context Protocol server that provides AI assistants access to AWS CloudWatch Logs, enabling browsing, searching, summarizing, and correlating logs across multiple AWS services.

Provides tools for Claude to query local Claude Code token usage and cost data, enabling spend analysis and insights through natural language.

Enables tracing mcp-use tool callbacks and capturing tool errors and exceptions in Sentry via MCP middleware, without SDK changes or additional services.

Enables Google Gemini and any MCP-compatible client to securely monitor and manage hypervisor guests — starting, stopping, rebooting, snapshotting, rolling back, and backing up VMs and containers — through the Model Context Protocol over Streamable HTTP with OAuth 2.0/OIDC authentication.

Provides Claude plan usage data (session and weekly percentages) as an MCP tool by reading through a logged-in browser, enabling Claude to check its own remaining usage.

Enables querying and analyzing Claude Desktop/Code conversation history across all users on a machine, including conversation search, token usage statistics, model/tool insights, and opening a web dashboard for detailed visualization.

Enables Claude Code sessions to check account rate-limit headroom, local token spend, and live session status, with read-only MCP tools for limits, summaries, token usage, and session listing.

Enables a Claude Code agent to fetch remaining 5-hour and weekly subscription usage limits, reset times, and per-window breakdowns as JSON. It provides the same figures as /usage through a local, read-only tool.

Enables retrieving real Claude subscription usage statistics, including the 5-hour session window, weekly limit, and per-model limits, from the same endpoint Claude Code uses.

An MCP server that exposes Claude Code's real-time rate limit usage so that an orchestrator can check remaining capacity before launching subtasks.

Read-only AMD GPU monitoring for Claude on Linux — VRAM, temperature, clocks, power, and running ML processes via rocm-smi.

Reports your Claude subscription usage (5-hour and weekly limits) with a forecast and velocity recommendation, using Claude Code's existing OAuth session without requiring an API key.

Provides structured access to Claude Code agent log files, allowing agents to query assistant lines and tool calls without reading raw JSONL data.

Fetches and tracks Claude.ai usage data including session and weekly limits with automated daily logging and persistent session management. It allows users to monitor their usage history directly through Claude Code integrated tools.

Maintenance, recovery, and observability for Claude Code. CLI + MCP server + dashboard.

Provides comprehensive telemetry and usage analytics for Claude Code sessions, including token usage tracking, cost monitoring, and tool usage patterns. Enables users to monitor their Claude usage with detailed metrics, warnings, and trend analysis.

Enables real-time data streaming through Server-Sent Events with timestamp broadcasting and server monitoring capabilities. Optimized for deployment on Render.com with health checks and status endpoints.

Gives the model visibility into the same 5-hour session, weekly, and per-model usage percentages shown in Claude Code, along with reset times. It also lets a project cap how much of the weekly limit may be spent via start/check/end budget tools that report OK, LOW, or OVER_BUDGET.

Shows your current Claude Desktop activity as Discord Rich Presence, including model, status, usage, and subscription info.

Lets an AI agent check its own Claude and Codex usage limits — used percentages and exact reset times for session and weekly windows — so it can plan long-running work around resets instead of dying mid-task. It reads local, credential-free sources by default, always reports which source answered, and ships a hook that pushes quota state into context automatically.