check_container_number — Triplicate – export documents MCP Tool Read-only
check_container_number
(check container number) is one of 7 tools on the
Triplicate – export documents
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_container_number from your client
- Claude Code Triplicate – export documents check_container_number run in your project directory
- Claude Desktop Triplicate – export documents check_container_number ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Triplicate – export documents check_container_number ~/.cursor/mcp.json
- VS Code Triplicate – export documents check_container_number .vscode/mcp.json
- Zed Triplicate – export documents check_container_number ~/.config/zed/settings.json
- Windsurf Triplicate – export documents check_container_number ~/.codeium/windsurf/mcp_config.json
- Cline Triplicate – export documents check_container_number ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Triplicate – export documents check_container_number ~/.gemini/settings.json
- Grok Triplicate – export documents check_container_number .mcp.json (in your project root)
- ChatGPT Triplicate – export documents check_container_number Settings → Connectors → Advanced → Developer mode
- Claude.ai Triplicate – export documents check_container_number Settings → Connectors → Add custom connector
- LangChain Triplicate – export documents check_container_number pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http triplicate https://api.triplicatedocs.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 8 October 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.