shipper_profile — warp agent mcp MCP Tool
shipper_profile
(shipper profile) is one of 33 tools on the
warp agent mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call shipper_profile from your client
- Claude Code warp agent mcp shipper_profile run in your project directory
- Claude Desktop warp agent mcp shipper_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor warp agent mcp shipper_profile ~/.cursor/mcp.json
- VS Code warp agent mcp shipper_profile .vscode/mcp.json
- Zed warp agent mcp shipper_profile ~/.config/zed/settings.json
- Windsurf warp agent mcp shipper_profile ~/.codeium/windsurf/mcp_config.json
- Cline warp agent mcp shipper_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI warp agent mcp shipper_profile ~/.gemini/settings.json
- Grok warp agent mcp shipper_profile .mcp.json (in your project root)
- ChatGPT warp agent mcp shipper_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai warp agent mcp shipper_profile Settings → Connectors → Add custom connector
- LangChain warp agent mcp shipper_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http warp-agent-mcp https://mcp.wearewarp.com/api/mcp
Other tools on this server
- freight_workflow
- compare_freight_costs
- van_quote
- box_truck_quote
- ftl_quote
- ltl_quote
- ltl_market_options
- compare_modes
- batch_quote
- book
- batch_book
- multistop_quote
- multistop_book
- track
- lane_history
- list_bookings
- status
- events
- get_invoice
- get_documents
- quote_history
- login
- consolidate
- automate_lane
- manage_automation
- automation_receipts
- payment_status
- analytics
- locations
- load_templates
- save_load_template
- delete_load_template
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.