Step 1: Add the connector
Register https://mcp.cretask.com/mcp as an MCP server in your editor's Copilot configuration and sign in when Cretask asks. Access is granted per person, not per repository.
Step 2: Choose what it can reach
Cretask's authorization screen lists exactly what is being asked for: reading tasks and projects, creating and updating them, and adding notes. Read-only is a real choice if you only want GitHub Copilot to summarise your week. The grant can be narrowed or revoked at any time from Settings, Security, and the connector stops working the moment you do.
Step 3: Work in plain language
Ask for what you would ask a person. List my open tasks on this project. Add a task to retire the legacy webhook worker and put it in next week. GitHub Copilot resolves names, dates and projects against your live workspace rather than guessing at them, and tells you what it changed.
Step 4: Keep an audit trail
Every write is stamped with the actor, so a task GitHub Copilot created is visibly a task GitHub Copilot created, on the board and in the task's own history. Batched changes undo as one unit for thirty days, which is what makes it safe to hand over bulk work. Watch the first few runs, then let it run.