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