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