Skip to main content
Glama
MyLightIsOn

Lawrence's Personal MCP Server

by MyLightIsOn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Lawrence's Personal MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Frontend Tools Server

      ashios15
      F
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with frontend development tools including component scaffolding, bundle analysis, accessibility checks, and responsive design guidance. Enables automated generation of React components with tests and stories, bundle optimization recommendations, and WCAG compliance fixes.
      6
      -

    • Figma MCP Server

      anishtejwanigemi-max
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Figma files through tools that list projects/files, fetch design data, and generate React+Vite frontend code directly from Figma frames.
      4
      1,772 npm
      MIT

    • ds-mcp-sync

      blumaa
      F
      license
      A
      quality
      D
      maintenance
      Syncs design tokens and components from Figma to a Design System codebase, enabling automated generation of React components and Storybook stories.
      5
      -

    • Pixelbyte Figma MCP Server

      Rylaa
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables seamless integration with Figma API for extracting design tokens, generating production-ready code in multiple frameworks, capturing screenshots, and managing design assets directly from Figma.
      5
      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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct step in a design-to-code workflow, and the Figma, a11y, and codegen prefixes help separate concerns. However, figma_extract_design_tokens vs codegen_design_tokens and a11y_audit_component vs a11y_suggest_improvements are close enough that an agent might occasionally pick the wrong one.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun naming pattern within their respective domains, such as figma_get_file, a11y_audit_component, and codegen_react_component. The prefixes are predictable and group related functionality clearly.

    Tool Count5/5

    Eight tools is a well-scoped count for a server covering Figma access, accessibility auditing, and code generation. Each tool serves a distinct purpose, and the set feels neither bloated nor thin.

    Completeness5/5

    The tool surface covers the full intended workflow: fetching and searching Figma data, extracting design tokens, auditing components, generating components, and producing design token output. There are no obvious dead ends or critical missing operations for the apparent design-to-code purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources