"Trending MCP server for memory usage with GitHub Copilot integration" matching MCP servers:

An MCP server that retrieves current GitHub Copilot usage data, including quotas, limits, and usage statistics. It allows AI agents to monitor premium interaction status and detailed account usage via raw or formatted summaries.

Exposes GitHub Copilot premium request usage as an MCP tool, providing a breakdown by model and cost.

An MCP server that retrieves GitHub Copilot usage metrics and seat assignment data across Enterprise, Organization, and Team levels. It allows users to monitor code completions, chat activity, and active user counts through integrated tools.

Provides persistent memory for MCP-compatible agents (like Copilot CLI) to save and recall knowledge across sessions, plus long-running monitoring tools.

AI coding usage analytics — track spend, model usage, and costs across Cursor and Claude Code sessions.

MCP server that wraps Cursor Enterprise API to enable AI agents to answer questions about team spending, usage, and model adoption.

Audits local Claude Code transcripts to show which connected MCP servers are actually used, idle, failing, or awaiting authorization, and recommends which to keep or disconnect.

Exposes rate-limit and usage data for AI coding agent CLIs as MCP tools, enabling querying of usage snapshots and reset times.

Lets Claude look up your own Claude subscription usage limits — the same 5-hour and weekly percentages shown by /usage — mid-conversation, so it can pace long tasks and warn you before you hit a wall. It reads the local OAuth login, serves a throttled read-only snapshot (cached with graceful fallback), and exposes it as a single get_usage tool.

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 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.

MCP server for querying OpenAI usage and cost data, including spend summaries, daily breakdowns, month-over-month comparisons, and token usage by model.

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.

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.

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.

A local MCP server that exposes Blacksmith.sh's usage and cost data, enabling queries for CI spend through agents, alerts, or dashboards.

MCP server that reads local OpenClaw session files to provide token usage and cost data without any network calls or authentication.

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.

Enables Claude to read your Patch API budget usage, including spend, burn rate, and account details, directly from chat.