Description

GitHub has recently announced (June 12th) the availability of its official remote MCP server: https://github.blog/changelog/2025-06-12-remote-github-mcp-server-is-now-available-in-public-preview/

Tech details at https://github.com/github/github-mcp-server/blob/main/docs/remote-server.md

This GitHub server is available at https://api.githubcopilot.com/mcp/

Lots of use cases dealing with source code in Strands Agents will leverage this GitHub feature.

So, we believe that it's good - given the fact that GitHub server is permanently available - to include some tests in Strands's test harness to ensure that the integration keeps working.

This PR only contains 2 tests (list_tools and list commits) for now. But, we can augment it with tests for additional verbs if deemed useful.

Related Issues

N/A

Documentation PR

For these tests to run, a GitHub secret will have to be added on the repo. It has to contain the GitHub PAT allowing access to the chosen repo (this repo itself in this case).

The creation of this token is described at https://api.githubcopilot.com/mcp/

It used in the PR code this way: "headers": {HEADER_AUTHORIZATION: f"Bearer {MCP_GITHUB_PAT}"}

The GitHub workflow of the Strands Repo will have to be updated to supply this token to the build / test job as an env var.

I am happy to (just tell me):

1. update the workflow in a subsequent PR if you prefer
2. create a doc PR in official Strands doc to allow users to also leverage the MCP server easily.

Type of Change

New feature (by GitHub)

Testing

How have you tested the change? Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli

• [X ] I ran hatch run prepare

See attached pytest.log when running on my machine

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

pytest.log