get_component_api — Duck Framework MCP MCP Tool Read-only
get_component_api
(get component api) 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 get_component_api from your client
- Claude Code Duck Framework MCP get_component_api run in your project directory
- Claude Desktop Duck Framework MCP get_component_api ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Duck Framework MCP get_component_api ~/.cursor/mcp.json
- VS Code Duck Framework MCP get_component_api .vscode/mcp.json
- Zed Duck Framework MCP get_component_api ~/.config/zed/settings.json
- Windsurf Duck Framework MCP get_component_api ~/.codeium/windsurf/mcp_config.json
- Cline Duck Framework MCP get_component_api ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Duck Framework MCP get_component_api ~/.gemini/settings.json
- Grok Duck Framework MCP get_component_api .mcp.json (in your project root)
- ChatGPT Duck Framework MCP get_component_api Settings → Connectors → Advanced → Developer mode
- Claude.ai Duck Framework MCP get_component_api Settings → Connectors → Add custom connector
- LangChain Duck Framework MCP get_component_api 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.