Command: Configure MCP rules (via /o11y-engineer)
Goal: Generate IDE-specific rule files that embed Dynatrace DQL queries and observability context directly into the developer’s AI assistant.
MCP (Model Context Protocol) rules are configuration files that provide AI assistants with project-specific observability context. They embed DQL queries, service mappings, and debugging instructions so that developers can query telemetry directly from their IDE.
| IDE | Rule File Location | Format |
|---|---|---|
| Claude Code | .claude/commands/o11y/ |
Markdown |
| Cursor | .cursor/rules/ |
.mdc |
| Windsurf | .windsurfrules/ |
Markdown |
| Copilot | .github/copilot-instructions.md |
Markdown |
| Amazon Q | .amazonq/rules/ |
Markdown |
The agent asks which IDE you use and configures the output format accordingly.
The agent scans your project to discover:
You provide:
For each discovered service, the agent generates:
Rule files are written to the IDE-specific location in your project directory.
A manifest of generated rules is saved at observability-specs/mcp-rules-manifest.yaml.
MCP rules work best with the Dynatrace MCP server configured in your AI assistant. See Dynatrace Setup for configuration instructions.
After generating MCP rules, proceed to Phase 7: Implementation to hand off to the B-MAD agent ecosystem.