Insiders Feedback:

Open
#3,471 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
12/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
github, go
Domain
api

Research direction

The report names no tool, request, or token setup, only that a call-tool request failed with 403. Start by asking the reporter which tool was called, with what arguments, and which token scopes were in use, then try to reproduce it against the Go server. Done means the cause of the 403 is identified and either fixed or documented with the required permissions.

Written by the indexing model from the issue text.

Description

Version: Insiders

Feature:

Feedback:
call-tool failed:403

Dominant language
Go
Stars
34.2k
Forks
5.3k
Avg merge
5d 18h
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/github-mcp-server

All issues in github/github-mcp-server

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.