How can an AI agent control Tracy Profiler?

An MCP-compatible AI agent can use DCC-MCP to capture instrumented processes with Tracy and export bounded offline zone data for performance analysis. The agent selects the correct application instance or integration, discovers available tools, and reads their parameter definitions before acting and checking the result. These typed tools declare their inputs, outputs, and parameter types.

What can an AI agent do in Tracy Profiler?

• verify the target is instrumented and the official Tracy utilities are available.
• capture one bounded trace from the declared client address.
• export CSV data and summarize high-variance profiling zones.

Capabilities change with the adapter version and loaded Skills. Search and describe tools first instead of guessing current tool names from this page.

Safe operating flow

1. Install and follow the public dcc-mcp Skill.
2. Inspect the existing CLI, adapter, and live hosts; obtain consent before installing software or changing system state.
3. Use health, dcc-types, and list to verify the Gateway and target instance.
4. Search and describe tools for the actual Tracy Profiler task, then follow every returned next_step.
5. Make one bounded change and verify it through host state, files, previews, logs, or rendered output.

dcc-mcp-cli health
dcc-mcp-cli dcc-types
dcc-mcp-cli list

Copyable prompt

Use the dcc-mcp Skill to connect to my Tracy Profiler session. Inspect the existing CLI, adapter, and live instance first; ask before installing software or changing system state. Search for and describe typed tools related to "capture one bounded trace from the declared client address", then follow every returned next_step. Do not delete, overwrite, or publish existing work. Make the smallest verifiable change, then check the result against this requirement: "export CSV data and summarize high-variance profiling zones". Report the instance, tool, result, and evidence path.

Current availability and official source

The owning repository has independently released v0.2.5; it is not a host route in the verified Core 0.20.39 catalog. The target must already contain Tracy instrumentation. The adapter controls official capture/export utilities and does not inject profiling into an uninstrumented process. This refresh verified release metadata, not a new live-host run.

• Tracy Profiler adapter repository: source of truth for installation, compatibility, host-specific capabilities, and troubleshooting.
• All AI + DCC control guides: return to every public application and pipeline integration.
• Agent workflow: shared discovery, call, validation, and diagnostic steps.

This page describes the shared Agent workflow. Each integration's repository owns its installation, API, and compatibility details.