# An MCP agent checks prefab names and references

> Technical artists connect Claude Code to Unity MCP to scan new prefabs each night and report naming violations and missing references.

- Type: MCP integration
- Role: Technical art / QA
- Stage: Production
- Engine: Unity（2022.3 LTS）
- Tools: claude-code / unity-mcp
- Input: Paths of prefabs added or changed that day, plus the team naming guidelines
- Output: A Markdown table sent to the team chat with paths, issue types and suggested names

- Evidence: L3 Reproducible
- Checked: 2026-10-28

## Human review
- Maintain a manual allowlist for exceptions, such as outsourced assets and third-party plugins.
- Do not apply suggested names automatically: renaming can break string references outside GUIDs.

## Known limitations
- The first full scan of a large project takes time; process it in directory batches.

## Workflow

1. Nightly CI collects the paths of prefabs changed that day.
2. Claude Code reads the naming guidelines and uses Unity MCP to open each prefab, checking node names and component references.
3. Results are sent to the team chat as a table, for the asset owner to review the next day.

## Why include this case?

It turns a guideline document into a daily automated check, leaving people to handle exceptions.

## Sources
- [Example source: technical article](https://example.com/source-1)

Markdown source: https://gameaicases.com/en/cases/unity-prefab-naming-check/ · Game AI Cases · CC BY 4.0