get_api_usage — signals MCP Tool Read-only
get_api_usage
(get api usage) is one of 10 tools on the
signals
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_api_usage from your client
- Claude Code signals get_api_usage run in your project directory
- Claude Desktop signals get_api_usage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor signals get_api_usage ~/.cursor/mcp.json
- VS Code signals get_api_usage .vscode/mcp.json
- Zed signals get_api_usage ~/.config/zed/settings.json
- Windsurf signals get_api_usage ~/.codeium/windsurf/mcp_config.json
- Cline signals get_api_usage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI signals get_api_usage ~/.gemini/settings.json
- Grok signals get_api_usage .mcp.json (in your project root)
- ChatGPT signals get_api_usage Settings → Connectors → Advanced → Developer mode
- Claude.ai signals get_api_usage Settings → Connectors → Add custom connector
- LangChain signals get_api_usage pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http signals https://mcp.rivalsweeper.com/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.