MCP: Provisioning Artifact Generation

[yesoreyeram]

Parent: #7

Summary

Implement MCP support for generating provisioning artifacts for new and existing datasources.

Context

Agents should be able to produce YAML/Terraform artifacts for users who prefer infrastructure-as-code or copy-paste provisioning.

Scope

• YAML generation
• Terraform generation where feasible
• Existing datasource export
• New datasource config export
• Multi-datasource export
• Secret-safe output

Tasks

• Define YAML output format
• Define Terraform output format
• Generate YAML for one new datasource config
• Generate YAML for one existing datasource
• Generate YAML for multiple datasources
• Generate Terraform for one datasource where feasible
• Use placeholders/secret references for secure fields
• Add tests/snapshots for generated output

Deliverables

• YAML generation tool/API
• Terraform generation tool/API or documented follow-up
• Existing datasource export support
• Multi-datasource export support
• Secret-safe output behavior

Acceptance Criteria

• Agent can generate YAML for a datasource
• Agent can export YAML for existing datasource
• Agent can generate output for multiple datasources
• Secure fields are not emitted as plaintext
• Output is copy-pasteable
• Tests/snapshots cover generated output

Notes

YAML should be prioritized. Terraform can be implemented if feasible or documented as a follow-up.

[jcolladokuri]

Update:

Due to the fact that tools take up space in the user context regardless of whether they are used or not, the MCP team is careful about what should actually be a tool vs not.

Because in this case we are not actually producing anything (a new datasource in An instance for example) and we are simply generating a file that users will copy and paste into their environments. This will not be done as part of an MCP server tool but rather as skill as part of https://github.com/grafana/skills