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

feat: webarkit-studio MCP server

Open
  • Is something wrong?
#8 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
node.js, typescript
Domain
backend, developer-experience, tooling

Research direction

Start by reading the architecture notes for src/core, the Node runtime, and the existing work in #7 and #5. The issue proposes src/mcp/ or tools/mcp/ and lists the planned tools and tests, but the linked issues and implementation details will need review before choosing a starting task. Done means an agent can build a valid graph from catalog.list, run it on the test photo, and receive a found marker with a pose.

Written by the indexing model from the issue text.

Description

Part of Phase 2 / 3 (#1). Builds on #7; output format aligned with #5.

Context

The JSON graph is the source of truth and src/core depends on neither the editor nor the runtime. A thin MCP server over src/core and the Node runtime would let any MCP client (Claude Code, Copilot in VS Code, Cursor, Gemini CLI) author, validate, run and export graphs without the UI.

Proposed tools

  • catalog.list: node types, ports, params, defaults and live flags;
  • graph.validate: the same validation the studio uses;
  • graph.create, graph.edit: add or remove nodes, connect ports, set params;
  • tracking.run(graph, images | frames): runs the Node build through ArtkSession and returns per-frame results in the FrameResult shape of webarkit/jsartoolkitNFT#720;
  • export.bundle: the standalone app bundle.

Notes

  • Lives in src/mcp/ (or tools/mcp/), depends only on src/core and the runtime, never on src/editor.
  • When the facade from #5 lands, tracking.run switches to it. The tool output stays the same, so it doubles as a facade test harness.
  • A stdio transport is enough for a first version.

Tasks

  • Server skeleton (stdio) with catalog.list and graph.validate
  • graph.create / graph.edit
  • tracking.run on the Node build
  • export.bundle
  • Unit tests per tool; document the setup in AGENTS.md and the .mcp.json example

Acceptance

  • An agent builds a valid graph from catalog.list alone, runs it on the test photo and gets a found marker with a pose.

Generated by Claude Code

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
4m
Merged PRs (30d)
1

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.