"How to organize my email effectively" matching MCP servers:

Local-first MCP runtime for coding agents with bounded workspace access, content-preconditioned writes, AST search, LSP navigation and diagnostics, and Git status/diff. Designed to give coding agents useful repository access without treating unrestricted shell access as the default integration boundary.

Serves a git-backed folder of Markdown notes over MCP so AI agents can search, read, write, move and delete them, with every write recorded as a git commit attributed to the calling client. Supports full-text section search with snippets, wikilinks and typed relations, LFS-backed searchable attachments, optimistic concurrency for multiple agents, and per-client token or OAuth 2.1 access.

An MCP server that enables AI agents to retrieve detailed GitHub Pull Request information using git commit hashes, branch names, or PR numbers. It automatically detects repositories and extracts comprehensive PR data including descriptions, labels, and reviews via the GitHub CLI.

Provides access to a specific GitHub repository (my-notion) allowing AI assistants to browse files, read content, and track commit information. Enables real-time interaction with repository data through the GitHub API without authentication requirements.

Turns GitHub repository history into a cited maintainer skill for coding agents, providing tools to collect evidence, query the knowledge graph, and inspect bundles.

Lets AI agents turn a repository's git history into proposed GitHub issues grouped into units of work, each with a commit checklist and links, then create and close them only after approval. Planning is read-only and creation defaults to a dry run, skipping anything that already exists.

A local MCP server that turns AI clients into power users of local git repositories, enabling clone, browse, search, and inspect code without burning API tokens.

Converts Jenkins declarative pipelines into GitHub Actions workflow YAML files, facilitating migration from Jenkins to GitHub Actions CI/CD.

A read-only MCP server for the Bitbucket Cloud REST API v2.0 that enables AI assistants to browse workspaces, repositories, and review pull requests.

Provides tools for managing GitHub sub-issues and milestones, including adding/removing sub-issues, getting parent issues, and setting milestones.

A local MCP server that captures coding context, tracks developer sessions, and powers daily insights.

Provides AI assistants with access to personal best practice skills and coding guidelines stored as markdown files in a GitHub repository, enabling retrieval and listing of custom development standards.

Provides a read-only MCP bridge that lets Claude Web inspect workspace files, git state, and recorded test results while Codex remains the sole executor of changes.

A custom MCP server that lets AI assistants interact with GitHub accounts, offering tools for repository creation, file viewing, code search, and issue management.

Enables MCP clients to manage files in an isolated workspace and perform lightweight Git operations through a protected Streamable HTTP endpoint, including listing, reading, writing, searching, replacing, and deleting files plus checking status and diffs.

Enables MCP-compatible AI clients to connect to a Windows machine for file operations, PowerShell execution, Git inspection, task management, memory, and skills.

An MCP server that automates the backup of Cloudflare projects to a GitHub repository, providing a systematic way to preserve Cloudflare configurations and assets.

Enables phone-issued approve/commit/push/pull commands to control an AI coding agent's git actions by bridging GitHub webhooks and MCP tool calls.

Enables AI agents to intelligently organize Git changes into clean, focused commits with autopilot mode or surgical line-by-line staging precision. Supports partial staging of untracked files and handles large diffs with smart truncation.

Enables AI agents to create private GitHub issues for decisions, send email alerts, wait for human comments, and parse replies so work can resume. Supports guided setup and MCP integration without requiring separate AI API keys or an always-on cloud server.

Enables coding agents to query a codebase's git-history coupling graph to find blast radius, missing coupled files, explain why files change together via PRs/issues, and report how much of the graph was inspected.

Helps AI read GitHub repository structure and important files. Want to quickly understand what a repo is about? Prompt it with "read https://github.com/adhikasp/mcp-git-ingest and determine how the code technically works".

Enables Claude to manage GitHub Gists as an intelligent code library, allowing users to save, retrieve, update, and organize code snippets from anywhere with natural language commands.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Enables AI agents to run structured preflight checks and identity-scoped Git operations, committing, pushing and opening GitHub PRs with the correct Git name, email, SSH key and signature for each repository. Persistent changes require exact proposals, human approval by default and recoverable, idempotent apply.

Enables AI tools to browse the web as the user by providing access to a persistent browser session with logged-in accounts, supporting recipes for email, PRs, calendar, and more.

A server implementation demonstrating how AI models can interact with external tools and services through Model Context Protocol, featuring integrations for calculator functions, GitHub repositories, and Google Maps searches.

Enables the analysis of GitHub Pull Requests to extract metadata, commits, and code changes for structured AI insights. It also supports the optional creation of Notion pages to store and organize the resulting analysis.

Enables AI agents to discover GitHub repositories by expanding intents into multiple keyword queries, searching GitHub's live Search API, and returning deduplicated, ranked candidates with README excerpts and metadata.

Enables coding agents to verify whether a GitHub pull request is genuinely ready by checking draft state, conflicts, check results on the head commit, review requirements, merge queue status, and expected commit, returning a verdict with reasons and owners pinned to a commit and timestamp. It reports merged or closed PRs without judging them and never authorizes a merge.