azuga_get_profile — Azuga MCP by usefulapi MCP Tool
azuga_get_profile
(azuga get profile) is one of 16 tools on the
Azuga MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call azuga_get_profile from your client
- Claude Code Azuga MCP by usefulapi azuga_get_profile run in your project directory
- Claude Desktop Azuga MCP by usefulapi azuga_get_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Azuga MCP by usefulapi azuga_get_profile ~/.cursor/mcp.json
- VS Code Azuga MCP by usefulapi azuga_get_profile .vscode/mcp.json
- Zed Azuga MCP by usefulapi azuga_get_profile ~/.config/zed/settings.json
- Windsurf Azuga MCP by usefulapi azuga_get_profile ~/.codeium/windsurf/mcp_config.json
- Cline Azuga MCP by usefulapi azuga_get_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Azuga MCP by usefulapi azuga_get_profile ~/.gemini/settings.json
- Grok Azuga MCP by usefulapi azuga_get_profile .mcp.json (in your project root)
- ChatGPT Azuga MCP by usefulapi azuga_get_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai Azuga MCP by usefulapi azuga_get_profile Settings → Connectors → Add custom connector
- LangChain Azuga MCP by usefulapi azuga_get_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http azuga https://azuga.usefulapi.io/mcpOther tools on this server
- azuga_list_driver_scores
- azuga_list_trips
- azuga_get_trip_events
- azuga_list_events
- azuga_list_live_locations
- azuga_get_vehicle_location
- azuga_list_vehicles
- azuga_list_drivers
- azuga_list_groups
- azuga_list_geofences
- azuga_list_landmarks
- azuga_get_breadcrumbs
- azuga_list_pairing_history
- azuga_list_rewards
- azuga_get_vehicle_diagnostics
This list was read from the server itself, by connecting to it and calling tools/list on 7 November 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.