get_provider_limits — ai rate limit tracker MCP Tool Read-only
get_provider_limits
(get provider limits) is one of 4 tools on the
ai rate limit tracker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_provider_limits from your client
- Claude Code ai rate limit tracker get_provider_limits run in your project directory
- Claude Desktop ai rate limit tracker get_provider_limits ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ai rate limit tracker get_provider_limits ~/.cursor/mcp.json
- VS Code ai rate limit tracker get_provider_limits .vscode/mcp.json
- Zed ai rate limit tracker get_provider_limits ~/.config/zed/settings.json
- Windsurf ai rate limit tracker get_provider_limits ~/.codeium/windsurf/mcp_config.json
- Cline ai rate limit tracker get_provider_limits ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ai rate limit tracker get_provider_limits ~/.gemini/settings.json
- Grok ai rate limit tracker get_provider_limits .mcp.json (in your project root)
- ChatGPT ai rate limit tracker get_provider_limits Settings → Connectors → Advanced → Developer mode
- Claude.ai ai rate limit tracker get_provider_limits Settings → Connectors → Add custom connector
- LangChain ai rate limit tracker get_provider_limits pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ai-rate-limit-tracker https://api.lazy-mac.com/ai-rate-limit-tracker/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.