Skip to main content
Glama

Related Servers

Alternatives to DingCard

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to import Canva share links as editable templates, read and update template layers (text, images, positions, styling), and render PNG, JPEG, WebP, or PDF variants from data — singly or in bulk up to 25 at a time. Connects via a remote OAuth endpoint, API key, or local stdio.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Render PDFs and images from HTML templates (Jinja2, Liquid, Handlebars) or Word and PowerPoint files through the Formfeed API, check data against a template's schema before rendering, and convert Office documents to PDF.
      10
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Product mockup rendering API for e-commerce and print-on-demand. Upload Photoshop PSD templates, render photorealistic mockups by placing your designs onto smart object layers. 9 tools including AI-powered render (no PSD needed), template management, and account info. Supports remote HTTP (OAuth) and local stdio (npx) transports.
      265 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create high-resolution marketing images from simple JSON configs without design skills or API keys. Provides presets, themes, and layouts to render deterministic PNGs locally.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Turns photos plus a short brief into finished social-media designs such as stories, carousels, reel covers and invites. It searches and ranks templates, uploads images, places photos and copy, and returns rendered designs with links for further editing.
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 22 tools

    Disambiguation4/5

    Each tool has a well-described distinct role, but there are five creation entry points (from_content, from_outline, from_template, from_html, create_poster_from_content) whose boundaries an agent must infer from content-shape nuances, and three quality tools (validate_document= schema, inspect_document= structure, check_document= visual problems) whose names alone don't clearly separate them. The detailed descriptions do resolve most confusion, so it lands at mostly-distinct with a few confusable pairs.

    Naming Consistency4/5

    A strong snake_case verb_noun convention dominates: create_*_from_*, get_document, list_templates, add_decorations, apply_actions, check_document, render_markdown, share_document. The exceptions are minor — server_projects is a bare noun multiplexed by an action param, and add_template_pages/add_decorations mix patterns but stay readable.

    Tool Count3/5

    22 tools is on the heavy side for a card-design server, and part of that weight is genuine overlap: five separate document-creation tools plus three inspection/validation tools could be consolidated behind parameters. Every tool does earn a place in the workflow, but the surface feels broader than strictly necessary.

    Completeness4/5

    The lifecycle is nearly end-to-end: authoring (template/content/outline/HTML/poster), editing (apply_actions), validation/inspection/visual checking, rendering, local editor handoff, sharing, server project management, plus asset/template/stock-image discovery. Minor gaps exist — no document deletion, duplication, or local document listing — but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues