LabscoMCP early access ↗
AStheTECHMCP SERVER

MewCP Github MCP

Manage GitHub repositories, issues, pull requests, releases and branch protection through typed tools with a consistent response envelope.

by AStheTECH ↗Git Hosting & Code ReviewCommunity

LABSCO SUMMARY

GitHub with the governance surface included and a uniform error contract.

Two things set it apart from the usual GitHub wrapper: branch protection, review protection and repository rulesets are first-class tools, and every response uses the same envelope with a retriable flag, a retry_after_seconds hint and a machine-readable error code — so an agent knows whether to retry rather than guessing from a message. Writes that overwrite, like update_repository, return before and after state so the change is recoverable in the transcript.

What it is

A hosted GitHub MCP server on the MewCP platform. It covers repository content and administration — files and commits, issues and sub-issues, the pull request lifecycle including reviews, and governance settings such as branch protection and repository rulesets — with your GitHub credential connected once at the platform rather than pasted per client.

What you get

  • get_repo, create_repository, update_repository and fork_repository — read a repository's details, create one in an account or organization, rename or change its metadata (the response carries both before and after state), or fork it
  • get_file_contents, create_or_update_file and push_files — read a file, write one with SHA validation to prevent accidental overwrites, or push a multi-file commit
  • list_branches, list_commits, get_commit, list_tags, get_tag, list_releases, get_latest_release and get_release_by_tag — the repository's history and release surface
  • list_issues, get_issue, create_issue, update_issue, add_issue_comment, get_issue_comments and sub_issue_write — issue tracking including parent and sub-issue relationships
  • list_pull_requests, pull_request_read, create_pull_request, update_pull_request, update_pull_request_branch and merge_pull_request — the pull request lifecycle from open to merge
  • pull_request_review_write, add_reply_to_pull_request_comment, request_copilot_review and assign_copilot_to_issue — write a review, reply in a comment thread, and hand work to Copilot
  • search_repositories, search_code, search_users, search_issues and search_pull_requests — search across GitHub by each object type
  • get_branch_protection, set_branch_protection, delete_branch_protection, get_pull_request_review_protection, update_pull_request_review_protection and delete_pull_request_review_protection — branch and review requirements
  • list_repository_rulesets, get_repository_ruleset, create_repository_ruleset, update_repository_ruleset and delete_repository_ruleset — repository rulesets
  • get_label, list_org_repositories_by_contributor and get_me — a label, an organization's repositories filtered by contributor, and the authenticated identity

Requirements

A MewCP account with an active API key, and a GitHub credential connected there by OAuth or as a static key. Clients connect to the MewCP gateway and send the API key as Authorization: Bearer — the one header MewCP's page for this server asks for. GitHub's own OAuth scopes still govern what the credential can do.

Setup effort

Add the hosted endpoint plus a key — paste it into your client, then supply credentials

See installation options