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