build-mcp-server

To design an MCP server for Claude, you first identify target connections, audience, and required UI inputs. The skill then guides you through selecting the correct deployment model and tool pattern to ensure Claude can effectively use your SaaS API.

Yes, remote streamable-HTTP is one of the supported MCP deployment models for Claude integration. It is selected when your use case requires remote connections, often paired with OAuth and structured elicitation for upstream authentication.

The best way to structure MCP tool schemas is choosing between a one tool per action pattern or a search and execute pattern. This decision keeps schemas understandable and performant based on your specific action count.

Yes, building an MCP server supports local filesystem and desktop app integrations. The design process evaluates your specific integration scenario and recommends local stdio or other appropriate deployment models for desktop environments.

You should use MCPB or MCP app widgets when your MCP server requires rich UI widgets or structured elicitation. The design process evaluates these requirements during use case discovery to determine if they are necessary.

An MCP server handles structured elicitation by utilizing specific deployment models like MCP app widgets. This allows Claude to gather complex user inputs and interact with rich UI components during tool execution.