A remote MCP server that gives MCP clients authenticated access to GitHub: repos, issues, pull requests, file contents, and search, over a proper OAuth 2.1 handshake. Runs on Cloudflare Workers.
This MCP server provides detailed GitHub repository information by integrating with mcp.deepwiki.com and GitHub API to fetch repository wiki content, README files, and enable intelligent question-answering about repositories.
Model Context Protocol server that enables interaction with GitHub repositories, issues, pull requests, and search functionality through natural language.
MCP server for GitHub code retrieval and reuse, using SQLite+FTS5 indexing and search history to enable search-first, requirements-refined code search from GitHub repositories.
Provides comprehensive access to GitHub repositories, issues, pull requests, commits, user profiles, and statistics through 10 tools with natural language query support and advanced search capabilities.
Read-only MCP server for GenieLocker that exposes tools for service status, commercial inventory, live quotes, recipe search, and credit pricing, without enabling purchases or model inference.
Enables multiple AI agents to collaborate on the same git repository by coordinating work via a shared claims branch, detecting file conflicts before they happen.
CodebaseAgent-MCP is an MCP server that uses a lightweight RAG pipeline to delegate repository analysis to a dedicated OpenAI-compatible LLM, reducing token consumption by having the primary assistant receive only the relevant findings instead of repeatedly scanning the entire codebase.
MCP server that lets Claude diagnose failed GitHub Actions runs by fetching and parsing CI logs into structured failure signals, enabling natural-language questions like 'Why did the last run fail?'.
Generates multi-platform release announcements (X, Reddit, GitHub profile, awesome-list, MCP directory) and a publish-readiness checklist for any public GitHub repository.
An MCP server that gives AI agents structured read/write access to a story-based project backlog. Agents can list stories, read content, update status, and append notes — all backed by plain markdown files that live inside your project repository.
There is no shared server. The backlog files live in your repo under requirements/, committed and versioned alongside your code
Enables AI to read and analyze repository incident scan results, including file diffs and summaries, to help investigate suspicious changes. It is read-only and does not execute code or send data externally.
Enables AI assistants to interact with Atlassian Jira Cloud, allowing users to manage projects, issues, comments, and workflows through natural language commands.