Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat: creative tool pipeline for markers and assets (Blender, ComfyUI, Krita)

Open
  • Is something wrong?
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
blender, typescript
Domain
computer-vision, tooling

Research direction

Read the linked issues #2, #1, and #8 to understand the authoring and MCP context, then check the Blender, ComfyUI, and Krita projects for current setup details. Start with the trackability check described here: feature-point density and distribution from the NFT generator. Done means documenting setup in docs/agents/creative-tools.md, adding the check and example pipeline, and recording asset provenance and licenses.

Written by the indexing model from the issue text.

Description

Part of Phase 2: Authoring (#2, #1). Optional and local; uses the MCP server from #8.

Context

Authoring a WebAR scene needs two kinds of assets: marker images that track well and 3D models. Creative tools now expose MCP servers that agents can drive.

Tools (status checked in October 2026)

  • Blender: the official Blender Lab MCP server (v1.0.x). It is not compatible with the community "MCP for Blender" (formerly ahujasid/blender-mcp). Use: create or convert glTF models for the scene nodes and the planned glTF support.
  • ComfyUI: the official local Comfy-Org/comfy-mcp (beta, stdio, needs comfy-cli and a running ComfyUI; AGPL-3.0 or commercial). Use: marker images and textures.
  • Krita: community servers only (for example krita-codex-mcp, Windows-first). Experimental. Use: retouch marker images.

Pipeline

image (ComfyUI / Krita) → trackability check (feature-point density and distribution from the NFT generator) → NFT dataset → glTF model (Blender) → graph (MCP server, #8).

The trackability check is the key piece: NFT needs texture-rich, non-repetitive images, and generated images often are not. It also prepares the roadmap's in-editor dataset generation.

Constraints

  • No creative tool becomes a project dependency; the setup lives in docs/agents/creative-tools.md, not in the shared .mcp.json.
  • Generated assets are not committed (as with npm run assets); record the provenance and license of each asset.
  • Server versions and protocols move fast: check each project before documenting the setup.

Tasks

  • Trackability check (script, then a tool of the MCP server)
  • docs/agents/creative-tools.md with the setup for Blender, ComfyUI and Krita
  • Example: generated marker → dataset → graph with a glTF model

Generated by Claude Code

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
2d 15m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from webarkit/webarkit-studio

All issues in webarkit/webarkit-studio

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.