Using Agents and MCP Servers with GitHub Copilot and Xcode to Create a Points App - Part 1
Agents and MCP Servers are used to create a Points App with Xcode and GitHub Copilot for Xcode. The app shall track points for multiple players for board games. Atlassian JIRA and Confluence are integrated using MCP servers to manage work and documentation.
Part 1
This setup showcases an AI-augmented development workflow that combines MCP-based tool integrations, Copilot-driven task generation, and repository-defined ticket schemas to improve consistency and reduce manual overhead across connected tools.
I created a JIRA ticket with brief information about the purpose of the app and its main features. GitHub Copilot for Xcode was used to create three subtasks in JIRA. Atlassian was integrated using MCP servers. Ticket format was specified in a github instructions file.
Instruction File
An instructions file has been added with information about the detail and format of JIRA tickets. It includes directions to strictly follow the formatting hints in the instruction file, use shorter wordings and stick to the existing requirements without adding new ones.
Creation of Tasks
GitHub Copilot for Xcode was tasked with generating JIRA tickets for a Points App. After receiving a detailed description of the app’s features, Copilot was prompted to draft proposed JIRA ticket descriptions. In a second step, Copilot created the actual JIRA tickets by leveraging the Atlassian MCP Server integration.
▶ Play video in full resolution
Creation of Subtasks
To break the work down into manageable units, it was divided into clearly defined subtasks. Providing explicit guidance to Copilot on how to structure and separate the work items is essential. In this example, the work was organized into the following areas: Main View, Adding Points, and Managing Players. Copilot was then prompted to create the corresponding subtasks in JIRA.
▶ Play video in full resolution
Subtasks
The subtasks were successfully created in JIRA and properly linked to their respective parent tasks, ensuring a clear and well-structured organization of the overall work. This structured breakdown improves transparency and makes it easier to understand how individual efforts contribute to the broader feature development.
As a result, the JIRA overview now provides meaningful visibility into the current status of feature development and overall project progress. Team members and stakeholders can quickly see which tasks are completed, in progress, or still pending, supporting better coordination and more effective planning.
