Github MCP server has only half its claimed tools available

[ichoosetoaccept]

Describe the bug
I've set this up in Claude for desktop: https://github.com/modelcontextprotocol/servers/tree/HEAD/src/github
This server claims to offer 16 tools, making it a powerful way to interact with Github via Claude:

• create_or_update_file: Create or update a single file in a repository
• push_files: Push multiple files in a single commit
• search_repositories: Search for GitHub repositories
• create_repository: Create a new GitHub repository
• get_file_contents: Get contents of a file or directory
• create_issue: Create a new issue
• create_pull_request: Create a new pull request
• fork_repository: Fork a repository
• create_branch: Create a new branch
• list_issues: List and filter repository issues
• update_issue: Update an existing issue
• add_issue_comment: Add a comment to an issue
• search_code: Search for code across GitHub repositories
• search_issues: Search for issues and pull requests
• search_users: Search for GitHub users
• list_commits: Gets commits of a branch in a repository
• get_issue: Gets the contents of an issue within a repository

I'd love for this list to actually be true. I only get half those tools max when I ask Claude about it:

To Reproduce
Steps to reproduce the behavior:

1. Install the Anthropic reference Github MCP server: https://github.com/modelcontextprotocol/servers/tree/HEAD/src/github
2. Interact with a Github repository
3. Create an issue (should work)
4. Ask Claude to update or get the issue (will fail)

Expected behavior
I expect this MCP server to actually provide all the tools that listed under tools on this page: https://github.com/modelcontextprotocol/servers/tree/HEAD/src/github

Logs
Not applicable since the server is working as it should, I suppose, just with a subset of the tools it's supposed to have.

Thanks for reading!

[Aschent89]

@ichoosetoaccept If you are using MCP servers that are part of the Releases from MCP here on Github, those are all behind what is on latest and PR'd (last update was December 4th, 2024). You'll need to ensure that you're pointing your config files at the index.js for the server you want to use (after cloning [and/or forking] the repo and ensuring contents are updated).

[apappascs]

there is a bug in a few methods of github server for: list_issues, update_issue, add_issue_comment, and get_issue tools where their return schema is not following the specification https://github.com/modelcontextprotocol/specification/blob/main/schema/schema.json#L80
this PR is fixing those issues #396

[ichoosetoaccept]

@ichoosetoaccept If you are using MCP servers that are part of the Releases from MCP here on Github, those are all behind what is on latest and PR'd (last update was December 4th, 2024). You'll need to ensure that you're pointing your config files at the index.js for the server you want to use (after cloning [and/or forking] the repo and ensuring contents are updated).

Yes, we discussed this on Discord (hi!) but I couldn't get it to work. The proper way of fixing this issue, however, is by actually fixing the Github MCP server's code and not with workarounds I suppose. Thanks anyway!

there is a bug in a few methods of github server for: list_issues, update_issue, add_issue_comment, and get_issue tools where their return schema is not following the specification https://github.com/modelcontextprotocol/specification/blob/main/schema/schema.json#L80 this PR is fixing those issues #396

Excellent, many thanks for your PR! I hope it gets merged soon 😊

[jpshack-at-palomar]

This is also described in #541

[jpshack-at-palomar]

Fixed by #728