GitHub
by GitHub (Community)
Description
GitHub MCP — access repositories, issues, pull requests, and code search via the GitHub Copilot MCP endpoint.
Capabilities
No special capabilities listed
AI Agent Discovery
GitHub is indexed by Tedix as a structured developer tools listing for AI assistants, search crawlers, and users comparing agent-ready apps.
- GitHub is categorized as Developer Tools.
- Developer: GitHub.
- Connector type: AI-Powered App.
- Current connector status: Connected.
- Observed distribution channels: official.
Use this page to understand whether GitHub is relevant for developer tools workflows in AI assistants.
For MCP discovery, this listing helps crawlers connect GitHub to tool, resource, prompt, and server-health signals instead of treating it as a generic directory entry.
The canonical Tedix directory URL is https://tedix.dev/apps/github/.
Crawlable Profile
Source and availability
Tedix identifies GitHub from Upstream Mcp tool source; Store sources: Official MCP registry; Distribution: Individual.
- Official MCP registry Auth not flagged
Auth, tools, and actions
Authentication: Requires Login. No special capability flags are currently listed. Current MCP inventory reports 43 tools, 3 resources, and 2 prompts.
- add_comment_to_pending_review · App action
Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure).
- add_issue_comment · App action
Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments.
- add_reply_to_pull_request_comment · App action
Add a reply to an existing pull request comment. This creates a new comment that is linked as a reply to the specified comment.
- create_branch · App action
Create a new branch in a GitHub repository
- create_or_update_file · App action
Create or update a single file in a GitHub repository. If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations. In order to obtain the SHA of original file version before updating, use the following git command: git rev-parse <branch>:<path to file> SHA MUST be provided for existing file updates.
- create_pull_request · App action
Create a new pull request in a GitHub repository.
- create_repository · App action
Create a new GitHub repository in your account or specified organization
- delete_file · High-impact write action
Delete a file from a GitHub repository
Plus 35 additional actions in the full tool inventory.
Verification freshness
- Catalog synced March 17, 2026
- Connector checked May 30, 2026
- MCP scanned May 30, 2026
- Website enriched May 28, 2026
- Directory updated May 30, 2026
Alternatives and related apps
Comparable apps in Developer Tools include 3Min API, Adalo, Airbyte Agent Engine, Alchemy.
Publisher Intelligence
Insights and recommendations for app publishers. See how your app performs and how to improve discoverability.
Server Status github-mcp-server vgithub-mcp-server/remote-36cb90f7ca12f9d569d7611a3e949456ed1ae6e5
https://api.githubcopilot.com/mcp/ Last checked: May 30, 2026
Technical Details
Tools(43)
Showing 43 of 43 tools
| Tool | Description | Flags | Test | Last Tested | |
|---|---|---|---|---|---|
add_comment_to_pending_review | Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure). | — | 0%Latency 254ms | May 30, 2026 | |
add_issue_comment | Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments. | — | 0%Latency 76ms | May 30, 2026 | |
add_reply_to_pull_request_comment | Add a reply to an existing pull request comment. This creates a new comment that is linked as a reply to the specified comment. | — | 0%Latency 78ms | May 30, 2026 | |
create_branch | Create a new branch in a GitHub repository | — | 0%Latency 77ms | May 30, 2026 | |
create_or_update_file | Create or update a single file in a GitHub repository. If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations. In order to obtain the SHA of original file version before updating, use the following git command: git rev-parse <branch>:<path to file> SHA MUST be provided for existing file updates. | — | 0%Latency 102ms | May 30, 2026 | |
create_pull_request | Create a new pull request in a GitHub repository. | — | 0%Latency 81ms | May 30, 2026 | |
create_repository | Create a new GitHub repository in your account or specified organization | — | 0%Latency 76ms | May 30, 2026 | |
delete_file | Delete a file from a GitHub repository | destructive | 0%Latency 84ms | May 30, 2026 | |
fork_repository | Fork a GitHub repository to your account or specified organization | — | 0%Latency 82ms | May 30, 2026 | |
get_commit | Get details for a commit from a GitHub repository | read-only | 0%Latency 99ms | May 30, 2026 | |
get_file_contents | Get the contents of a file or directory from a GitHub repository | read-only | 0%Latency 77ms | May 30, 2026 | |
get_label | Get a specific label from a repository. | read-only | 0%Latency 81ms | May 30, 2026 | |
get_latest_release | Get the latest release in a GitHub repository | read-only | 0%Latency 86ms | May 30, 2026 | |
get_me | Get details of the authenticated GitHub user. Use this when a request is about the user's own profile for GitHub. Or when information is missing to build other tool calls. | read-only | 0%Latency 79ms | May 30, 2026 | |
get_release_by_tag | Get a specific release by its tag name in a GitHub repository | read-only | 0%Latency 79ms | May 30, 2026 | |
get_tag | Get details about a specific git tag in a GitHub repository | read-only | 0%Latency 81ms | May 30, 2026 | |
get_team_members | Get member usernames of a specific team in an organization. Limited to organizations accessible with current credentials | read-only | 0%Latency 78ms | May 30, 2026 | |
get_teams | Get details of the teams the user is a member of. Limited to organizations accessible with current credentials | read-only | 0%Latency 78ms | May 30, 2026 | |
issue_read | Get information about a specific issue in a GitHub repository. | read-only | 0%Latency 390ms | May 30, 2026 | |
issue_write | Create a new or update an existing issue in a GitHub repository. | — | 0%Latency 83ms | May 30, 2026 | |
list_branches | List branches in a GitHub repository | read-only | 0%Latency 81ms | May 30, 2026 | |
list_commits | Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100). | read-only | 0%Latency 77ms | May 30, 2026 | |
list_issue_types | List supported issue types for repository owner (organization). | read-only | 0%Latency 80ms | May 30, 2026 | |
list_issues | List issues in a GitHub repository. For pagination, use the 'endCursor' from the previous response's 'pageInfo' in the 'after' parameter. | read-only | 0%Latency 79ms | May 30, 2026 | |
list_pull_requests | List pull requests in a GitHub repository. If the user specifies an author, then DO NOT use this tool and use the search_pull_requests tool instead. | read-only | 0%Latency 77ms | May 30, 2026 | |
list_releases | List releases in a GitHub repository | read-only | 0%Latency 72ms | May 30, 2026 | |
list_repository_collaborators | List collaborators of a GitHub repository. Results are paginated; the response includes `nextPage`, `prevPage`, `firstPage`, and `lastPage` fields. To get the next page, use the `nextPage` value as the `page` parameter. | read-only | 0%Latency 354ms | May 30, 2026 | |
list_tags | List git tags in a GitHub repository | read-only | 0%Latency 71ms | May 30, 2026 | |
merge_pull_request | Merge a pull request in a GitHub repository. | — | 0%Latency 73ms | May 30, 2026 | |
pull_request_read | Get information on a specific pull request in GitHub repository. | read-only | 0%Latency 70ms | May 30, 2026 | |
pull_request_review_write | Create and/or submit, delete review of a pull request. Available methods: - create: Create a new review of a pull request. If "event" parameter is provided, the review is submitted. If "event" is omitted, a pending review is created. - submit_pending: Submit an existing pending review of a pull request. This requires that a pending review exists for the current user on the specified pull request. The "body" and "event" parameters are used when submitting the review. - delete_pending: Delete an existing pending review of a pull request. This requires that a pending review exists for the current user on the specified pull request. - resolve_thread: Resolve a review thread. Requires only "threadId" parameter with the thread's node ID (e.g., PRRT_kwDOxxx). The owner, repo, and pullNumber parameters are not used for this method. Resolving an already-resolved thread is a no-op. - unresolve_thread: Unresolve a previously resolved review thread. Requires only "threadId" parameter. The owner, repo, and pullNumber parameters are not used for this method. Unresolving an already-unresolved thread is a no-op. | — | 0%Latency 73ms | May 30, 2026 | |
push_files | Push multiple files to a GitHub repository in a single commit | — | 0%Latency 75ms | May 30, 2026 | |
request_copilot_review | Request a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer. | — | 0%Latency 72ms | May 30, 2026 | |
run_secret_scanning | Scan files, content, or recent changes for secrets such as API keys, passwords, tokens, and credentials. This tool is intended for targeted scans of specific files, snippets, or diffs provided directly as content. The files parameter accepts either a single string or an array of strings containing raw file contents or diff hunks, and returns detected secrets with their locations and related secret scanning metadata. Content must not be empty. For full repository scanning, other mechanisms are available. Caveats: - Only files within the codebase should be scanned. Files outside of the codebase should not be sent. - Files listed in .gitignore should be skipped. | read-only | 0%Latency 75ms | May 30, 2026 | |
search_code | Fast and precise code search across ALL GitHub repositories using GitHub's native search engine. Best for finding exact symbols, functions, classes, or specific code patterns. | read-only | 0%Latency 94ms | May 30, 2026 | |
search_commits | Search for commits across GitHub repositories using GitHub's commit search syntax. Useful for finding specific changes, authors, or messages across one or many repositories. Searches the default branch only. | read-only | 0%Latency 322ms | May 30, 2026 | |
search_issues | Search for issues in GitHub repositories using issues search syntax already scoped to is:issue | read-only | 0%Latency 74ms | May 30, 2026 | |
search_pull_requests | Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr | read-only | 0%Latency 71ms | May 30, 2026 | |
search_repositories | Find GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub. | read-only | 0%Latency 80ms | May 30, 2026 | |
search_users | Find GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members. | read-only | 0%Latency 70ms | May 30, 2026 | |
sub_issue_write | Add a sub-issue to a parent issue in a GitHub repository. | — | 0%Latency 89ms | May 30, 2026 | |
update_pull_request | Update an existing pull request in a GitHub repository. | — | 0%Latency 73ms | May 30, 2026 | |
update_pull_request_branch | Update the branch of a pull request with the latest changes from the base branch. | — | 0%Latency 70ms | May 30, 2026 |
Discoverability Score
Fair
53 of 100 — how easily AI agents find your app
- Description quality14/20
- Example prompts0/20
- Keyword coverage0/15
- Tool metadata20/20
- Visual assets13/20
- Endpoint health10/10
- Data freshness7/15
How to Improve
Add at least 2 example prompts. Prompt examples strongly improve app matching and click-through intent.
Increase keyword coverage (discovery + trigger) to improve retrieval for long-tail queries.
Add at least 2 screenshots that show real workflows to increase confidence and conversion.
Metadata is stale (>30 days). Re-run sync/enrichment to keep listings current and reliable.
Technical Details
- Status
- ENABLED
- Type
- AI-Powered App
- Auth
- Requires Login
- Listed on
- Official
- Added
- March 17, 2026
- Last synced
- March 17, 2026
- Last checked
- May 30, 2026
- Version
- github-mcp-server/remote-36cb90f7ca12f9d569d7611a3e949456ed1ae6e5
- Distribution
- Individual