Azure DevOps MCP — XXX project scope
Scope
When using the user-ado (Azure DevOps) MCP server in this project, always restrict operations to the XXX project.
Default values
| Parameter | Value |
|---|---|
| project | XXX |
| team | XXX Team |
Instructions
- •Every ADO tool call: Pass
project: "XXX"when the tool accepts aprojectparameter. - •Tools that need a team (e.g.
wit_list_backlog_work_items,wit_list_backlogs,wit_get_work_items_for_iteration,core_list_project_teams): Also passteam: "XXX Team"when the tool accepts ateamparameter. - •Search/filter tools (e.g.
search_workitem): Useproject: ["XXX"]in the project filter. - •Override: Use a different project or team only when the user explicitly asks (e.g. "list issues in project X" or "show me the OtherProject board").
- •Creating work items: When creating a new ticket/work item:
- •Always create a User Story unless the user explicitly specifies a different work item type (e.g. Bug, Task, Epic).
- •Assign it to the current sprint based on today's date. Use
wit_list_team_iterationsto find the active iteration whose date range includes the current date, then set theSystem.IterationPathfield accordingly.
Examples
- •"List work items" → call with
project: "XXX". - •"List repos" → use project XXX.
- •"Run query X" → pass
project: "XXX". - •"List issues in Contoso" → use project "Contoso" (user override).