Skip to main content
subagent official · GitHub

octopus-release-notes-with-mcp — GitHub Copilot subagent

Creates Markdown release notes from Octopus Deploy releases. It pulls deployment commit details from GitHub and produces a structured summary.

Install into GitHub Copilot · Manually: put the files in place All methods and platforms ↓
.github/agents/octopus-deploy-release-notes-mcp.agent.md
Open on GitHub

What octopus-release-notes-with-mcp does

This subagent connects to Octopus Deploy using a local MCP server launched via npx -y @octopusdeploy/mcp-server. It inspects the latest deployment for a designated space, environment, and project.

From deployment build data, the agent retrieves Git commits via GitHub. It analyzes commit messages, authors, dates, and diffs while dropping entries that do not belong in release notes. It outputs a Markdown summary.

Execution depends on OCTOPUS_API_KEY and OCTOPUS_SERVER_URL credentials. Without these variables configured, the MCP server cannot authenticate to the Octopus Deploy API.

What it helps with

  • generate markdown release notes from Octopus Deploy releases
  • extract commit messages and authors from deployment builds
  • filter out non-essential commits from release summaries
  • summarize GitHub diffs for deployed releases

Example prompts for the agent

  • Generate release notes for the latest deployment of WebApp in Production
  • Summarize commits from the last release in the Default space for project CoreAPI

How to install octopus-release-notes-with-mcp

Manually: put the files in place

.github/agents/octopus-deploy-release-notes-mcp.agent.md

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about octopus-release-notes-with-mcp

How to install octopus-release-notes-with-mcp in GitHub Copilot?

Add the agent file to .github/agents/octopus-deploy-release-notes-mcp.agent.md in your repository.

What does octopus-release-notes-with-mcp do?

It queries Octopus Deploy for recent release details, pulls associated commit information from GitHub, and compiles a Markdown changelog.

What credentials does this subagent require?

You must supply OCTOPUS_API_KEY and OCTOPUS_SERVER_URL in your environment secrets, along with npx to run the MCP server.

Source text

octopus-deploy-release-notes-mcp.agent.md · MIT
---
name: octopus-release-notes-with-mcp
description: Generate release notes for a release in Octopus Deploy. The tools for this MCP server provide access to the Octopus Deploy APIs.
mcp-servers:
  octopus:
    type: 'local'
    command: 'npx'
    args:
    - '-y'
    - '@octopusdeploy/mcp-server'
    env:
      OCTOPUS_API_KEY: ${{ secrets.OCTOPUS_API_KEY }}
      OCTOPUS_SERVER_URL: ${{ secrets.OCTOPUS_SERVER_URL }}
    tools:
    - 'get_account'
    - 'get_branches'
    - 'get_certificate'
    - 'get_current_user'
    - 'get_deployment_process'
    - 'get_deployment_target'
    - 'get_kubernetes_live_status'
    - 'get_missing_tenant_variables'
    - 'get_release_by_id'
    - 'get_task_by_id'
    - 'get_task_details'
    - 'get_task_raw'
    - 'get_tenant_by_id'
    - 'get_tenant_variables'
    - 'get_variables'
    - 'list_accounts'
    - 'list_certificates'
    - 'list_deployments'
    - 'list_deployment_targets'
    - 'list_environments'
    - 'list_projects'
    - 'list_releases'
    - 'list_releases_for_project'
    - 'list_spaces'
    - 'list_tenants'
---

# Release Notes for Octopus Deploy

You are an expert technical writer who generates release notes for software applications.
You are provided the details of a deployment from Octopus deploy including high level release nots with a list of commits, including their message, author, and date.
You will generate a complete list of release notes based on deployment release and the commits in markdown list format.
You must include the important details, but you can skip a commit that is irrelevant to the release notes.

In Octopus, get the last release deployed to the project, environment, and space specified by the user.
For each Git commit in the Octopus release build information, get the Git commit message, author, date, and diff from GitHub.
Create the release notes in markdown format, summarising the git commits.

© github · MIT · github/awesome-copilot

Similar subagents

All subagents for DevOps and infrastructure →

From the same set949

The whole set →
PagerDuty Incident Responder A GitHub Copilot subagent that works through PagerDuty incidents: reads the context, hunts for recent code changes, and proposes a fix as a pull request. ★ 40,451repo stars Oracle-to-PostgreSQL Migration Expert Guides .NET and C# application migrations from Oracle to PostgreSQL. Scans data access layers, scaffolds xUnit integration suites, and drafts migration plans. ★ 40,451repo stars OpenAPI to Application Generator This subagent turns an OpenAPI specification into an application structure with code, configuration, and testing guidance. Use it when an API contract is ready. ★ 40,451repo stars one-shot-feature-issue-planner Converts a single feature request into a complete, issue-ready implementation plan without asking follow-up questions. ★ 40,451repo stars Expert Nuxt Developer Guides Nuxt 3 and Nitro development with TypeScript typing. Helps configure data fetching via useFetch, resolve hydration issues, and structure server routes. ★ 40,451repo stars New Relic Incident Response Agent A GitHub Copilot subagent that ties New Relic observability data to code changes so you can find the cause of a production incident. ★ 40,451repo stars Neon Performance Analyzer Identifies slow Postgres queries on Neon, tests schema fixes inside isolated database branches, and prepares PRs with execution metrics. ★ 40,451repo stars Neon Migration Specialist A GitHub Copilot subagent that rehearses Postgres migrations on Neon branches and leaves the main database alone. Useful when schema changes can't take downtime. ★ 40,451repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor