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