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