build-component — Open Components MCP Prompt
build-component
is one of 4 prompts on the
Open Components
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke build-component from your client
- Claude Code Open Components Prompt/build-component run in your project directory
- Claude Desktop Open Components Prompt/build-component ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Open Components Prompt/build-component ~/.cursor/mcp.json
- VS Code Open Components Prompt/build-component .vscode/mcp.json
- Zed Open Components Prompt/build-component ~/.config/zed/settings.json
- Windsurf Open Components Prompt/build-component ~/.codeium/windsurf/mcp_config.json
- Cline Open Components Prompt/build-component ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Open Components Prompt/build-component ~/.gemini/settings.json
- Grok Open Components Prompt/build-component .mcp.json (in your project root)
- ChatGPT Open Components Prompt/build-component Settings → Connectors → Advanced → Developer mode
- Claude.ai Open Components Prompt/build-component Settings → Connectors → Add custom connector
- LangChain Open Components Prompt/build-component pip install langchain-mcp-adapters
Other prompts on this server
Open Components also offers 21 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.