Skip to main content
Glama
jrlingyin888

SwiftForge MCP

by jrlingyin888
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to SwiftForge MCP

No user-submitted related servers found.

    Related Servers

    • vinance-recipes

      Austinnui
      A
      license
      A
      quality
      D
      maintenance
      MCP server providing access to a catalog of reusable React/Next.js component recipes (animations, charts, UI components) with usage examples, props documentation, and architecture notes, enabling AI assistants to generate production-ready code.
      3
      MIT

    • systra-tools

      roesmannamelie-alt
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to search and retrieve 500+ production-ready React and Tailwind UI sections, page recipes, and brand-styled components over MCP, along with imagery and social post templates.
      -

    • CRUX MCP Server

      JustineDevs
      A
      license
      Not graded
      quality
      C
      maintenance
      Federates UI component registries, enabling AI agents to fetch exact component code, dependencies, and setup prerequisites directly into the workspace. Includes sandboxed previews, anti-slop layout auditing, and offline-to-cloud telemetry sync.
      44 npm
      1
      MIT

    • ds-pilot

      lyse-labs
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes your design system components and tokens to AI agents, preventing duplicate component creation and hardcoded token values.
      9 npm
      9
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list_categories, list_components, search_components, get_component.

    Tool Count5/5

    Four tools is well-scoped for a curated SwiftUI component catalog, covering browsing, listing, searching, and fetching details without unnecessary clutter.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources