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