Start with this example
Task: summarise open issues in a public test repository. Required: read issue titles and bodies. Not required: create issues, change code, read private repositories.
Give your assistant a clear brief
Use a compatible tool you already have, or choose a reviewed guide below. This is a suggested learning exercise, not proof that a specific installation has been tested.
Using the current documentation of the GitHub MCP Server, propose the narrowest connection for summarising open issues in a public test repository. Explain the host requirements, authentication and which permissions can be omitted. Do not connect or modify anything. Link the documentation supporting the plan.
Check the result
The plan should explain why code changes and issue creation are not required. Check every permission against the current official documentation; do not assume a host supports every authentication method.
What to take away
A useful connection is defined by the job and its access needs. Protocol support alone does not establish compatibility.
