-
Notifications
You must be signed in to change notification settings - Fork 603
403 Resource not accessible by personal access token [] #283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@algoORgoal in an edit of this issue you accidentally pasted a Figma PAT token and it needs to be revoked. It was found by secret scanning and it should be considered leaked in public. Please do this ASAP to avoid issues with your account. I will also contact them and request they revoke the token. Remediation stepsFollow the steps below before you close this alert.
|
Hi @algoORgoal,
docker login -u <USER> -p <PAT> ghcr.io/github This is just a quick workaround, I'll try to see if there is any better solution for that. |
As a possible solution for the configuration (in vscode): {
"inputs": [
{
"type": "promptString",
"id": "github_token",
"description": "GitHub Personal Access Token",
"password": true
},
{
"type": "promptString",
"id": "github_user",
"description": "GitHub Username"
}
],
"servers": {
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
"ghcr.io/github/github-mcp-server"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${input:github_token}",
"DOCKER_USER": "${input:github_user}",
"DOCKER_PASSWORD": "${input:github_token}"
}
}
}
} |
Describe the bug
When attempting to create a pull request using the
mcp_github_create_pull_request
tool, the operation fails with a 403 error despite having what appears to be a valid personal access token configured.Affected version
server version v0.1.1 (7ab5d96) 2025-04-07T16:05:06Z
(Version information to be added after running the command)
Steps to reproduce the behavior
mcp_github_create_pull_request
mcp.json
Expected vs actual behavior
Expected behavior:
The pull request should be created successfully in the specified repository.
Actual behavior:
The operation fails with a 403 error:
Logs
Additional information
Have a nice day, @bruce
The text was updated successfully, but these errors were encountered: