modelcontextprotocol/registry
Watch
1
0
Fork
You've already forked registry
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Implement --token and MCP_GITHUB_TOKEN login support (#705)

Browse source 
<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
The following PR implements the missing support for logging in via
`--token` or `MCP_GITHUB_TOKEN`

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] My code follows the repository's style guidelines
- [ ] New and existing tests pass locally
- [ ] I have added appropriate error handling
- [ ] I have added or updated documentation as needed

## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->
Fixes: #698

---------

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
This commit is contained in:
Radoslav Dimitrov 2025-10-29 17:23:41 +02:00 • committed by GitHub
commit f5f08bc92d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 69 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/guides/publishing/github-actions.md
View file

@ -98,14 +98,25 @@ The workflow runs tests, builds your package, publishes to npm, and publishes to
### GitHub Personal Access Token
You can authenticate using a GitHub Personal Access Token in two ways:
**Option 1: Using the --token flag**
```yaml
- name: Login to MCP Registry
run: mcp-publisher login github --token ${{ secrets.GITHUB_TOKEN }}
env:
GITHUB_TOKEN: ${{ secrets.MCP_GITHUB_TOKEN }}
run: mcp-publisher login github --token ${{ secrets.MCP_GITHUB_TOKEN }}
```
Add `MCP_GITHUB_TOKEN` secret with a GitHub PAT that has repo access.
**Option 2: Using environment variable**
```yaml
- name: Login to MCP Registry
run: mcp-publisher login github
env:
MCP_GITHUB_TOKEN: ${{ secrets.MCP_GITHUB_TOKEN }}
```
**Note:** You must create a custom secret `MCP_GITHUB_TOKEN` with a GitHub Personal Access Token that has `read:org` and `read:user` scopes. The automatic `GITHUB_TOKEN` provided by GitHub Actions does not have these permissions and cannot be used.
### DNS Authentication