tattoo-brief-mcp
Related Servers
Alternatives to tattoo-brief-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables planning of a tattoo before consulting an artist by generating a Markdown brief with placement notes and artist questions, assessing per-detail blur risk and minimum suggested sizes for small tattoos, and producing line-art and negative prompts for AI tattoo generators. All three tools run locally over stdio, need no API keys, and return deterministic results.3MIT
- AlicenseNot gradedqualityBmaintenanceCreate AI tattoo design concepts from a text prompt in 13 styles and search a public tattoo gallery.608 npm1MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to turn vague creative ideas into structured Music DNA, clearer creative constraints, and generation-ready style briefs, with intent analysis, keyword suggestions, prompt patterns, and reusable resources. It supports text-first, provider-independent preparation for music-generation workflows without directly generating audio or requiring credentials.60MIT
- FlicenseNot gradedqualityCmaintenanceEnables ChatGPT to queue validated embroidery designs, compile constrained one-color designs, describe Brother SE700 limits, list queued jobs, and request phone-side transfers to a Brother SE700 after explicit user approval.-
- AlicenseAqualityCmaintenanceEnables deterministic, read-only design of OpenSora video prompts and shot plans, including prompt diagnosis and access to workflow guides, without generating videos or requiring API keys.4MIT
- AlicenseAqualityDmaintenanceHelps UGC creators interpret brand briefs, generate shot lists and deliverables, and identify red flags before production.717 npmMIT
TDQS
Scored across 3 tools
line_art_prompt and build_tattoo_brief both take a tattoo idea and return text, so an agent could momentarily hesitate over which produces the AI prompt versus the human-facing brief. Their descriptions do clarify the distinction (generator prompt + negative prompt vs. structured artist brief), and check_small_size_legibility is clearly separate.
All three names use snake_case, and two follow a verb_noun/verb_phrase pattern (build_tattoo_brief, check_small_size_legibility). line_art_prompt is a noun phrase rather than a verb-led name, a minor deviation from an otherwise consistent convention.
Three focused tools fit a narrow, well-defined pipeline (idea → brief → prompt → legibility check) with no filler. It sits at the thin end of the suggested range, but each tool has a distinct role, so it is not under-scoped.
The surface covers generating a prompt, building a brief, and a size-legibility heuristic, but there is no way to refine or update an existing brief/prompt after feedback, and no style or placement reference lookup. Agents can work around this by re-calling tools from scratch, but iteration is a real gap.