detect_reference — BerthTime MCP Tool
detect_reference
(detect reference) is one of 18 tools on the
BerthTime
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call detect_reference from your client
- Claude Code BerthTime detect_reference run in your project directory
- Claude Desktop BerthTime detect_reference ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BerthTime detect_reference ~/.cursor/mcp.json
- VS Code BerthTime detect_reference .vscode/mcp.json
- Zed BerthTime detect_reference ~/.config/zed/settings.json
- Windsurf BerthTime detect_reference ~/.codeium/windsurf/mcp_config.json
- Cline BerthTime detect_reference ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BerthTime detect_reference ~/.gemini/settings.json
- Grok BerthTime detect_reference .mcp.json (in your project root)
- ChatGPT BerthTime detect_reference Settings → Connectors → Advanced → Developer mode
- Claude.ai BerthTime detect_reference Settings → Connectors → Add custom connector
- LangChain BerthTime detect_reference pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http berthtime https://berthtime.com/api/v1/mcpOther tools on this server
- list_companies
- list_shipments
- list_shared_shipments
- get_shipment
- get_shipment_events
- list_arriving_shipments
- list_delayed_shipments
- list_carriers
- get_usage
- list_alert_rules
- list_support_requests
- track_shipment
- update_shipment_identifiers
- get_share_link
- create_share_link
- create_support_request
- archive_shipment
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.