get_api_usage — Apibara Vehicle Auction Data MCP Tool Read-only
get_api_usage
(get api usage) is one of 8 tools on the
Apibara Vehicle Auction Data
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 Apibara Vehicle Auction Data get_api_usage run in your project directory
- Claude Desktop Apibara Vehicle Auction Data get_api_usage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Apibara Vehicle Auction Data get_api_usage ~/.cursor/mcp.json
- VS Code Apibara Vehicle Auction Data get_api_usage .vscode/mcp.json
- Zed Apibara Vehicle Auction Data get_api_usage ~/.config/zed/settings.json
- Windsurf Apibara Vehicle Auction Data get_api_usage ~/.codeium/windsurf/mcp_config.json
- Cline Apibara Vehicle Auction Data get_api_usage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Apibara Vehicle Auction Data get_api_usage ~/.gemini/settings.json
- Grok Apibara Vehicle Auction Data get_api_usage .mcp.json (in your project root)
- ChatGPT Apibara Vehicle Auction Data get_api_usage Settings → Connectors → Advanced → Developer mode
- Claude.ai Apibara Vehicle Auction Data get_api_usage Settings → Connectors → Add custom connector
- LangChain Apibara Vehicle Auction Data get_api_usage pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vehicle-auction https://apibara.tech/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.