Best for
- Developers who need fast GitHub data access
- Projects that want to reduce GitHub API calls and latency
- Teams using Convex and Next.js
F
FasterGH
Community
A fast GitHub mirror UI backed by Convex as a real-time cache
GitHub source repository ↗
50FMRS · D
FasterGH is a technically robust GitHub mirror tool, but it is not an official MCP server and requires self-hosting and configuration. It offers a rich set of operational tools and real-time caching, but is best suited for experienced developers.
FasterGH is a GitHub mirror UI that uses Convex as a real-time cache/sync layer, keeping GitHub as the source of truth and Convex as the low-latency read model. It streams GitHub webhook events into Convex for real-time updates, backfills historical data on repo onboarding, and provides a read-optimized UI that never hits the GitHub API on page load. Write operations like creating issues, commenting, and merging PRs are supported via optimistic mutations backed by GitHub API. Ideal for developers who need fast access to GitHub data and want to reduce API call latency and rate limits.
Tools
connectRepo
Connect a GitHub repository for mirroring
listRepos
List all mirrored repositories
listPRs
List pull requests for a repository
listIssues
List issues for a repository
getActivity
Get activity feed data
createIssue
Create a new GitHub issue
createComment
Create a comment on an issue or PR
mergePR
Merge a pull request
adminHealth
Get system health status and table counts
Setup
- Clone the repository and install dependencies:
bun install. 2. Copy the environment file:cp .env.example .envand set GITHUB_WEBHOOK_SECRET, CONVEX_DEPLOYMENT, and NEXT_PUBLIC_CONVEX_URL. 3. Set Convex environment variables: inpackages/database, runbunx convex env set GITHUB_PAT "$(gh auth token)"andbunx convex env set GITHUB_WEBHOOK_SECRET "<your-webhook-secret>". 4. Start the development server:bun dev. 5. Use theconnectRepomutation to connect a GitHub repository. 6. Set up a repo-level webhook pointing to the Convex deployment's/api/github/webhookendpoint.
Fit and risk
Not for
- Users needing full GitHub functionality
- Individuals who prefer not to deploy additional backend services
- Non-developers or technical novices
Required permissions
- Requires a GitHub Personal Access Token (PAT) with `repo` scope to read and write repository data
- Requires a Convex deployment and corresponding environment variables
- Requires a public endpoint to receive webhooks
Risks and side effects
- Potential for stale data due to sync lag
- Data inconsistency if webhooks are misconfigured
- Operational overhead of maintaining Convex database and webhook infrastructure
Troubleshooting
- Ensure the GitHub PAT is valid and has `repo` scope. Verify webhook configuration points to the Convex `/api/github/webhook` endpoint with the correct secret. Check Convex deployment status and environment variables. Inspect logs for errors and run the test suite.
Use cases
Quickly browse GitHub pull requests
Real-time view of GitHub issue updates
Create comments and merge PRs
Monitor repository activity
Supported clients
Claude DesktopFull support