SwiftForge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_categoriesA | List the SwiftForge component categories with how many curated SwiftUI components each holds. Call this first to see what's available. |
| list_componentsA | List curated SwiftUI components (id, title, category, description, minIOS, tags). Optionally filter by category. Use get_component to fetch the full source for one. |
| search_componentsA | Search the curated SwiftUI catalog by free text (matches title, description, tags, category). Returns brief results; follow up with get_component for full source. Prefer this when the user describes a UI need (e.g. 'glass card', 'pull to refresh', 'onboarding'). |
| get_componentA | Fetch one curated SwiftUI component by id, including full production-ready, current-API source code, usage example, and notes. Paste the returned Swift directly into the project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
list_categories and get_component are clearly distinct. list_components and search_components overlap somewhat as both return component lists, but their filter/search purposes are described well enough to avoid major confusion.
All tool names follow a consistent snake_case verb_noun pattern: list_categories, list_components, search_components, get_component.
Four tools is well-scoped for a curated SwiftUI component catalog, covering browsing, listing, searching, and fetching details without unnecessary clutter.
The tool surface covers the full read-only lifecycle of the catalog: discover categories, list/filter components, search by free text, and retrieve full component source. No critical gap for the stated purpose.