Project Customization MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_API_KEY | No | API key for tool authorization. Required only for executing tools; resources and prompts work without it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_projectB | Analyze a VS Code project structure and detect project type, frameworks, languages, and customization opportunities |
| generate_copilot_instructionsC | Generate a .github/copilot-instructions.md file based on project analysis and best practices |
| update_readmeC | Update or create README.md with project guidelines and best practices |
| get_customization_recommendationsC | Get recommendations for customizing VS Code settings, instruction files, and project guidelines |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-and-customize | Comprehensive prompt to analyze a VS Code project and set up customization files (instructions, README, guidelines) |
| generate-instructions-only | Generate only the Copilot custom instructions file based on project analysis |
| review-and-improve | Review existing project customizations and suggest improvements |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Project Metadata | |
| Project Structure | |
| Current Guidelines | |
| Project README |
TDQS
Scored across 4 tools
analyze_project and get_customization_recommendations both surface customization opportunities, creating some overlap. However, generate_copilot_instructions and update_readme clearly target distinct output files, and the descriptions help distinguish the intended use cases.
All four tools use consistent snake_case verb_noun naming: analyze_project, generate_copilot_instructions, update_readme, and get_customization_recommendations. The verbs are clear and the pattern is predictable throughout.
Four tools is well-scoped for a project customization utility, covering analysis, generation, updating, and recommendations without bloat or excessive thinness. Each tool has a distinct role in the workflow.
The surface covers analysis, copilot instruction generation, README updates, and recommendations, but there is no tool to actually create or update VS Code settings or extensions files. This leaves a notable dead end for the settings-customization part of the stated purpose.