Request for Feedback on Experimental Bicep MCP Tools in VSCode
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 79
Description
Please share constructive or positive feedback on the [Experimental Bicep MCP Tools in VSCode](https://github.com/Azure/bicep/blob/main/docs/experimental/mcp-tools.md).
Some questions to get the gears turning:
1. Have you, and how often, been using the new MCP tools in your Bicep authoring process?
2. What use cases do you tend to use the MCP tools for? I.e. complex authoring with multiple resources you are not familiar with, fixing dependency errors, simple authoring patterns to reduce toil, etc.
3. Have you had any trouble getting started with the tools?
4. What tools have you been missing or looking for?
5. How is the server working for you within VSCode? Do you use another editor? What would be your preferred server type, i.e. local, remote, within VSCode, etc.
For those of you who haven't tried out the Experimental Bicep MCP tools yet, you can follow along with [Tutorial Bicep Experimental MCP tools - YouTube](https://www.youtube.com/watch?v=LeGpeY1LrBU)
Contributor guide
Research direction
Start with docs/experimental/mcp-tools.md and the linked tutorial, then try the experimental MCP tools in VSCode. Provide constructive feedback covering usage, use cases, setup difficulties, missing tools, and preferred server or editor experience; the work is done when those observations are shared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100