Skip to main content
Glama
Doyajin174

teguma

by Doyajin174
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to teguma

No user-submitted related servers found.

    Related Servers

    • 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.
      22 npm
      9
      MIT

    • figmind

      guhcostan
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI clients to Figma, enabling real-time reading, creation, and modification of designs using natural language.
      MIT

    • figma-pilot

      youware-labs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create, modify, and manage Figma designs through natural language commands via a specialized MCP server and plugin bridge. It supports a wide range of operations including element creation, property modification, component management, and accessibility checks.
      9 npm
      106
      MIT

    • figma-mcp-rust

      alvinindra
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enables AI tools to read and write Figma designs via a plugin bridge, bypassing the Figma REST API and rate limits.
      52
      MIT

    • Figma Agent MCP

      TrungLee003
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that connects AI clients to Figma via a WebSocket bridge and native plugin, enabling deterministic design operations like inspection, creation, mutation, styling, validation, and optimization.
      14 npm
      1
      MIT

    • @designjs/mcp-server

      rubychilds
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI coding agents to read and write to a local-first HTML/CSS design canvas, bridging visual design and code generation.
      1
      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 24 tools

    Disambiguation4/5

    Most tools have distinct resource+action targets, but a few could be confused: create_design_document sounds like creation while actually validating, and get_design_context overlaps with get_tokens/get_constraints/get_components as a compressed summary. Descriptions generally clarify the intended use, so the ambiguity is limited.

    Naming Consistency5/5

    All tool names follow a consistent lower_snake_case verb_noun pattern with clear verbs like get, list, create, update, delete, import, export, save, load. The few prepositonal names such as create_from_template still follow the same stylistic convention.

    Tool Count3/5

    With 24 tools, the server is at the heavy end of the range for a single MCP server. The count is defensible because it covers both Penpot design-system interaction and design-document automation, but it still feels like a lot for an agent to navigate efficiently.

    Completeness3/5

    The server covers core workflows well: extracting design context, importing designs, editing Penpot elements, generating/validating documents, exporting, and saving/loading projects. Notable gaps include no delete or update operation for saved design projects, no obvious blank-document creation path, and create_design_document only validates despite its name.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources