GitHub
by OpenAI(Community)
Visitor takeaway
66/100
Fair AI-discovery coverage across description, prompts, keywords, visuals, tool metadata, health, and freshness.
Routing category
Developer Tools
This app has a primary category, so visitors can browse and compare it in the right directory context.
Connector evidence
Reachable
Tedix can reach this MCP endpoint and can show live capability evidence when tools are discovered.
Directory freshness
1d ago
Catalog metadata was refreshed 1d ago (September 6, 2026).
Description
Explore repository files, documentation, folder structures, and commit history to understand code, prepare reviews, or document a project. Summarize pull requests, clarify how parts of the codebase fit together, or turn technical details into approachable explanations when sharing work with others.
Website Preview
App Screenshots
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: OpenAI.
- Connector type: AI-Powered App.
- Current connector status: Connected.
- Observed distribution channels: chatgpt, official.
- Available regions: FR, US, GB, ES, KR, IN.
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: ChatGPT app store, Official MCP registry; Distribution: Ecosystem Directory; Tenant install: prepared. Availability is reported for FR, US, GB, ES, KR, IN.
- ChatGPT app storeAuth required · RELEASED · FR, US, GB, ES, KR, IN
- Official MCP registryAuth not flagged
Auth, tools, and actions
Authentication: Requires Login. No special capability flags are currently listed. Current MCP inventory reports 47 tools, 4 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 and/or reaction to a specific issue or issue comment in a GitHub repository. Use this tool with pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add or react to review comments. At least one of body or reaction is required.
- add_reply_to_pull_request_comment · App action
Add a reply and/or reaction to an existing pull request comment. This can create a new comment linked as a reply to the specified comment, add an emoji reaction to the specified comment, or do both. At least one of body or reaction is required.
- assign_copilot_to_issue · Repeatable action
Assign Copilot to a specific issue in a GitHub repository. This tool can help with the following outcomes: - a Pull Request created with source code changes to resolve the issue More information can be found at: - https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-cloud-agent
- 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. To obtain the current blob SHA before updating, call the get_file_contents tool with the same owner, repo, and path, and set its ref parameter to this tool's branch value. The first text result reports the blob SHA for the requested path. SHA MUST be provided for existing file updates.
- create_pull_request · App action
Create a new pull request in a GitHub repository.
- create_pull_request_with_copilot · App action
Delegate a task to GitHub Copilot coding agent to perform in the background. The agent will create a pull request with the implementation. You should use this tool if the user asks to create a pull request to perform a specific task, or if the user asks Copilot to do something.
Plus 39 additional actions in the full tool inventory.
Verification freshness
- Catalog synced1d ago (September 6, 2026)
- Connector checked5h ago (September 7, 2026)
- MCP scanned5h ago (September 7, 2026)
- Website enrichedMay 28, 2026
- Directory updated5h ago (September 7, 2026)
Publisher Intelligence
Public trust signals for visitors and practical recommendations for publishers. Use this section to understand what Tedix can verify today and what would make the app easier for AI agents to find.
Visitor takeaway
66/100
Fair AI-discovery coverage across description, prompts, keywords, visuals, tool metadata, health, and freshness.
Routing category
Developer Tools
This app has a primary category, so visitors can browse and compare it in the right directory context.
Connector evidence
Reachable
Tedix can reach this MCP endpoint and can show live capability evidence when tools are discovered.
Directory freshness
1d ago
Catalog metadata was refreshed 1d ago (September 6, 2026).
Server Statusgithub-mcp-server vgithub-mcp-server/remote-3ec14fdb2e4c747a3b2846e8c8f0d92fe7bd39f0
https://api.githubcopilot.com/mcp/Last checked: 5h ago
Server Instructions
The GitHub MCP Server provides tools to interact with GitHub platform. Tool selection guidance: 1. Use 'list_*' tools for broad, simple retrieval and pagination of all items of a type (e.g., all issues, all PRs, all branches) with basic filtering. 2. Use 'search_*' tools for targeted queries with specific criteria, keywords, or complex filters (e.g., issues with certain text, PRs by author, code containing functions). Context management: 1. Use pagination whenever possible with batches of 5-10 items. 2. Use minimal_output parameter set to true if the full information is not needed to accomplish a task. Tool usage guidance: 1. For 'search_*' tools: Use separate 'sort' and 'order' parameters if available for sorting results - do not include 'sort:' syntax in query strings. Query strings should contain only search criteria (e.g., 'org:google language:python'), not sorting instructions. Always call 'get_me' first to understand current user permissions and context. ## Issues Check 'list_issue_types' first for organizations to use proper issue types. Use 'search_issues' before creating new issues to avoid duplicates. Always set 'state_reason' when closing issues. ## Pull Requests PR review workflow: Always use 'pull_request_review_write' with method 'create' to create a pending review, then 'add_comment_to_pending_review' to add comments, and finally 'pull_request_review_write' with method 'submit_pending' to submit the review for complex reviews with line-specific comments. Before creating a pull request, search for pull request templates in the repository. Template files are called pull_request_template.md or they're located in '.github/PULL_REQUEST_TEMPLATE' directory. Use the template content to structure the PR description and then call create_pull_request tool.
Technical Details
Tools(47)
Showing 47 of 47 tools
| Flags | Test | ||||
|---|---|---|---|---|---|
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 353ms | Jul 29, 2026 | |
add_issue_comment | Add a comment and/or reaction to a specific issue or issue comment in a GitHub repository. Use this tool with pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add or react to review comments. At least one of body or reaction is required. | — | 0%Latency 87ms | Jul 29, 2026 | |
add_reply_to_pull_request_comment | Add a reply and/or reaction to an existing pull request comment. This can create a new comment linked as a reply to the specified comment, add an emoji reaction to the specified comment, or do both. At least one of body or reaction is required. | — | 0%Latency 88ms | Jul 29, 2026 | |
assign_copilot_to_issue | Assign Copilot to a specific issue in a GitHub repository. This tool can help with the following outcomes: - a Pull Request created with source code changes to resolve the issue More information can be found at: - https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-cloud-agent | — | 0%Latency 71ms | Aug 1, 2026 | |
create_branch | Create a new branch in a GitHub repository | — | 0%Latency 397ms | Jul 31, 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. To obtain the current blob SHA before updating, call the get_file_contents tool with the same owner, repo, and path, and set its ref parameter to this tool's branch value. The first text result reports the blob SHA for the requested path. SHA MUST be provided for existing file updates. | — | 0%Latency 95ms | Jul 31, 2026 | |
create_pull_request | Create a new pull request in a GitHub repository. | — | 0%Latency 97ms | Jul 31, 2026 | |
create_pull_request_with_copilot | Delegate a task to GitHub Copilot coding agent to perform in the background. The agent will create a pull request with the implementation. You should use this tool if the user asks to create a pull request to perform a specific task, or if the user asks Copilot to do something. | — | 0%Latency 32ms | Aug 1, 2026 | |
create_repository | Create a new GitHub repository in your account or specified organization | — | 0%Latency 98ms | Jul 31, 2026 | |
delete_file | Delete a file from a GitHub repository | destructive | 0%Latency 98ms | Jul 31, 2026 | |
fork_repository | Fork a GitHub repository to your account or specified organization | — | 0%Latency 97ms | Jul 31, 2026 | |
get_commit | Get details for a commit from a GitHub repository | read-only | 0%Latency 97ms | Jul 31, 2026 | |
get_copilot_job_status | Get the status of a GitHub Copilot coding agent job. Use this to check if a previously submitted task has completed and to get the pull request URL once it's created. Provide the job ID (from create_pull_request_with_copilot) or pull request number (from assign_copilot_to_issue), or any pull request you want agent sessions for. | read-only | 0%Latency 5ms | Aug 1, 2026 | |
get_file_contents | Get the contents of a file or directory from a GitHub repository | read-only | 0%Latency 96ms | Jul 31, 2026 | |
get_label | Get a specific label from a repository. | read-only | 0%Latency 98ms | Jul 31, 2026 | |
get_latest_release | Get the latest release in a GitHub repository | read-only | 0%Latency 99ms | Jul 31, 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 97ms | Jul 31, 2026 | |
get_release_by_tag | Get a specific release by its tag name in a GitHub repository | read-only | 0%Latency 97ms | Jul 31, 2026 | |
get_tag | Get details about a specific git tag in a GitHub repository | read-only | 0%Latency 97ms | Jul 31, 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 99ms | Jul 31, 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 98ms | Jul 31, 2026 | |
issue_read | Get information about a specific issue in a GitHub repository. | read-only | 0%Latency 98ms | Jul 31, 2026 | |
issue_write | Create a new or update an existing issue in a GitHub repository. | — | 0%Latency 98ms | Jul 31, 2026 | |
list_branches | List branches in a GitHub repository | read-only | 0%Latency 106ms | Jul 31, 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 98ms | Jul 31, 2026 | |
list_issue_fields | List issue fields for a repository or organization. Returns field definitions including name, type (text, number, date, single_select), and for single_select fields the list of valid option names. When repo is omitted, returns org-level fields directly. | read-only | 0%Latency 651ms | Jun 29, 2026 | |
list_issue_types | List supported issue types for a repository or its owner organization. When repo is omitted, returns org-level issue types directly. | read-only | 0%Latency 98ms | Jul 31, 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 97ms | Jul 31, 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 97ms | Jul 31, 2026 | |
list_releases | List releases in a GitHub repository | read-only | 0%Latency 97ms | Jul 31, 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 97ms | Jul 31, 2026 | |
list_tags | List git tags in a GitHub repository | read-only | 0%Latency 96ms | Jul 31, 2026 | |
merge_pull_request | Merge a pull request in a GitHub repository. | — | 0%Latency 102ms | Jul 31, 2026 | |
pull_request_read | Get information on a specific pull request in GitHub repository. | read-only | 0%Latency 98ms | Jul 31, 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 98ms | Jul 31, 2026 | |
push_files | Push multiple files to a GitHub repository in a single commit | — | 0%Latency 97ms | Jul 31, 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 101ms | Jul 31, 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 97ms | Jul 31, 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 96ms | Jul 31, 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 477ms | Aug 13, 2026 | |
search_issues | Search issues using natural-language semantic matching. Best for conceptual or paraphrased queries (e.g. "login fails after password reset"). Already scoped to is:issue. | read-only | 0%Latency 110ms | Jul 31, 2026 | |
search_pull_requests | Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr | read-only | 0%Latency 96ms | Jul 31, 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 98ms | Jul 31, 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 97ms | Jul 31, 2026 | |
sub_issue_write | Add a sub-issue to a parent issue in a GitHub repository. | — | 0%Latency 103ms | Jul 31, 2026 | |
update_pull_request | Update an existing pull request in a GitHub repository. | — | 0%Latency 97ms | Jul 31, 2026 | |
update_pull_request_branch | Update the branch of a pull request with the latest changes from the base branch. | — | 0%Latency 25ms | Aug 1, 2026 |
Discoverability Score
Fair
66 / 100
How easily AI agents can find this app from its current catalog metadata.
- Description quality20/20
- Example prompts0/20
- Keyword coverage0/15
- Category clarity5/5
- Tool metadata20/20
- Visual assets13/20
- Endpoint health10/10
- Data freshness15/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.
Technical Details
- Status
- ENABLED
- Type
- AI-Powered App
- Auth
- Requires Login
- Listed on
- ChatGPTOfficial
- Added
- February 20, 2026
- Last synced
- 1d ago
- Last checked
- 5h ago
- Version
- github-mcp-server/remote-3ec14fdb2e4c747a3b2846e8c8f0d92fe7bd39f0
- Distribution
- Ecosystem Directory