Skip to content

Add MCP server as a primitive type to the sample package#2

Draft
Copilot wants to merge 2 commits intomainfrom
copilot/implement-plugin-installation-support
Draft

Add MCP server as a primitive type to the sample package#2
Copilot wants to merge 2 commits intomainfrom
copilot/implement-plugin-installation-support

Conversation

Copy link

Copilot AI commented Mar 9, 2026

Extends the APM sample package to demonstrate MCP (Model Context Protocol) server support — the missing primitive type for plugins that ship MCP servers alongside agents, prompts, and instructions.

Changes

  • .apm/mcps/github.mcp.json — New MCP server definition using the GitHub MCP server via Docker, establishing the .apm/mcps/ discovery path convention
  • apm.yml — Added mcp dependencies section parallel to existing apm section; bumped description to include MCP servers
  • README.md — Added MCP Server row to primitives table; split Dependencies section to show both apm and mcp dependency types

MCP declaration format

# apm.yml
dependencies:
  apm:
    - github/awesome-copilot/skills/review-and-refactor
  mcp:
    - io.github.github/github-mcp-server

MCP server config lives in .apm/mcps/*.mcp.json and is auto-discovered by APM on apm install.

Original prompt

Start implementation

The user has attached the following file paths as relevant context:

  • .github/instructions/doc-sync.instructions.md
  • .github/copilot-instructions.md
  • .github/copilot-instructions.md
  • AGENTS.md
[Chronological Review: The conversation began with the user inquiring about the warning message for a new version of APM (v0.7.5) while they were on v0.7.4. The user then requested to remove their local cache file. After installing v0.7.5, the user reported still seeing v0.7.4 when checking the version, leading to questions about the functionality of "apm update." The user expressed concerns about the update process being broken for their scenario. The conversation shifted to discussing the implementation of a pull request for plugin installation support and the dependencies on other pull requests. The user emphasized the need for careful planning and questioned the design decisions regarding definitions resolution. They suggested auto-discovery for missing components and finally requested to start the implementation.]

[Intent Mapping:

  1. "I think it has a warning message that there is a new version published (v0.7.5) that should trigger if I use it." - User wants to verify version update functionality.
  2. "remove my local cache file" - User requests cache removal.
  3. "I installed the v0.7.5 but I still get the v0.7.4 when I do apm --version." - User seeks to troubleshoot version installation.
  4. "som y 'apm update' experience is broken for my scenario?" - User questions the update process.
  5. "Now #201 is done. We need MCP installation support for plugins who ship MCPs." - User outlines next steps for implementation.
  6. "are you sure this is a solid, scalable implementation design?" - User seeks confirmation on design robustness.
  7. "Plan carefully now" - User emphasizes the need for strategic planning.
  8. "why do you need the definitions resolution with those 3 things?" - User questions design choices.
  9. "ok, auto-discover when missing, update the plan accordingly" - User suggests a modification to the plan.
  10. "Start implementation" - User initiates the implementation phase.]

[Technical Inventory:

  • APM (Atom Package Manager) v0.7.4 and v0.7.5: Version management and update functionality.
  • MCP (Multi-Component Plugin) installation support: Required for plugins that ship MCPs.
  • GitHub pull requests: Reference to specific PRs (#208 for plugin installation support, #201 for MCP installation pipeline).]

[Code Archaeology:

  • Files mentioned:
    • /Users/danielmeppiel/Repos/awd-cli/tests/integration/test_version_notification.py
    • /Users/danielmeppiel/Repos/awd-cli/tests/unit/test_version_checker.py
  • Changes were made to these files, but specific modifications were not detailed in the conversation.]

[Progress Assessment:

  • Completed Tasks: User has installed v0.7.5 and implemented PR #208 for plugin installation support.
  • Partially Complete Work: MCP installation support is pending, as it relies on the completion of PR #201, which is now done. The user is currently planning and starting the implementation phase.]

[Context Validation: All critical information for continuation is captured, including the need for MCP installation support and the user's emphasis on careful planning and design considerations.]

[Recent Commands Analysis:

  • Last Agent Commands: User executed commands related to APM version checks and cache removal.
  • Tool Results Summary: User reported issues with version visibility after executing "apm update."
  • Pre-Summary State: The agent was actively discussing the implementation of MCP installation support and planning the next steps when the token budget was exceeded.
  • Operation Context: The commands executed were directly related to the user's goal of ensuring proper version management and initiating the implementation of new features.]
1. Conversation Overview: - Primary Objectives: User aimed to verify the functionality of APM version updates, troubleshoot installation issues, and initiate the implementation of MCP installation support. - Session Context: The conversation flowed from version management concerns to implementation planning for plugin support, with a focus on design robustness and strategic planning. - User Intent Evolution: The user transitioned from troubleshooting version issues to outlining implementation steps and emphasizing careful planning.
  1. Technical Foundation:
  • APM: Version 0.7.4 and 0.7.5, used for managing Atom packages.
  • MCP: Required for plugins that ship multiple components, with installation support being a key focus.
  1. Codebase Status:
  • /Users/danielmeppiel/Repos/awd-cli/tests/integration/test_version_notification.py:
    • Purpose: Testing version notifications.
    • Current State: Recent edits made, specifics not detailed.
  • /Users/danielmeppiel/Repos/awd-cli/tests/unit/test_version_checker.py:
    • Purpose: Unit testing for version checking functionality.
    • Current State: Rec...

Created from VS Code.


🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Co-authored-by: danielmeppiel <51440732+danielmeppiel@users.noreply.github.com>
Copilot AI changed the title [WIP] Start implementation of plugin installation support Add MCP server as a primitive type to the sample package Mar 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants