CodeFizz
ToolsDemoDocsRoadmapChangelogPricingFAQ
Get the plugin

Getting Started

  • Introduction
  • Quick Start
  • Requirements
  • Installing the CLI
  • License & Machines

Guides

  • Installing the Plugin
  • The AI Skill
  • CLI vs MCP
  • Multiple Editors
  • How It Works
  • Discovering Commands

Walkthroughs

  • Build a Blueprint with AI
  • Author a Material Graph
  • Create a Niagara System

Reference

  • Reference
  • Niagara
  • PCG
  • Materials
  • StateTree
  • Sequencer
  • Level Actors
  • Project Settings
  • Blueprints
  • Blueprint Structs
  • Enhanced Input
  • Asset Management
  • Bulk Asset Ops
  • Data Assets
  • Object Properties
  • UMG Widgets
  • Data Tables
  • Curves
  • Console Commands
  • Profiling
  • Core
  • Debug

Help

  • FAQ
  • Troubleshooting
  • For AI Agents
DocsReferenceDebug

Debug

Every Debug command in CodeFizz Editor Agent, with parameters and examples.

Loading…
PreviousCoreNextFAQ
CodeFizz

A drop-in Unreal Engine 5 plugin that exposes the entire editor surface (Blueprints, Materials, Niagara, PCG, StateTree, Insights profiling, and more) over the Model Context Protocol. Connect Claude Code, Cursor, VS Code, or any MCP-compatible client and let your AI build inside the engine.

Product

  • Features
  • Docs
  • Tools
  • Demo
  • Roadmap
  • Changelog
  • Pricing
  • FAQ

Resources

  • Install guide
  • Discord
  • YouTube
  • Open-source edition
  • Manage subscription

Legal

  • Refund Policy
  • Privacy Policy
  • Terms of Service

© 2026 CodeFizz. All rights reserved.

CodeFizz Editor Agent is a CodeFizz product. Payments processed by Polar Software, Inc. (Polar), the Merchant of Record.

2 commands. Each shows its parameters and an example, and has a copyable deep link, so you (or an AI agent) can jump straight to one.

set_mcp_debug

Enable or disable MCP debug mode (token tracking)

Toggles MCP debug mode which enables token usage tracking on every MCP command. When enabled, the bridge measures the approximate token size of each request and response, accumulates totals per command, and tracks call counts. Use get_mcp_token_stats to read the accumulated statistics. Useful for identifying which commands produce oversized responses that waste LLM context budget.

ParameterTypeRequiredDescription
enabledboolNoEnable debug mode
example
cfa set_mcp_debug --enabled
cfa set_mcp_debug --enabled=false
get_mcp_token_stats

Get MCP token usage statistics

Returns accumulated token usage statistics from the MCP bridge. Shows per-command call counts, total input/output tokens, and averages. Only collects data when debug mode is enabled via set_mcp_debug. Use this to audit which MCP commands consume the most tokens and optimize your workflow accordingly.

example
cfa get_mcp_token_stats