"Using Local MySQL Data for Search and Chat Functionality" matching MCP servers:

A local, zero-dependency MCP server that cuts coding-agent round-trips by aggregating search, read, edit, exec, git, and savings tools into single, validated calls, with cost tracking and no data leaving the machine.

Odds are, most of what you want to build is already open source. Tell your AI agent what you're making, and it finds it: which repos to use as they are, which to adapt, and what's left for you to write. Every repo it names is real, licensed for your use or flagged, and checked live.

Enables AI clients like ChatGPT or Codex to manage files and local Git repositories within an explicitly authorized workspace, with server-enforced path boundary checks and optional remote Git operations.

A local MCP server that connects Claude Desktop, Claude Code, and Claude Chat to your Azure DevOps organization, enabling querying work items, reviewing pull requests, triggering pipelines, searching code, managing test plans, and updating wikis using plain language.

For people who want their AI to run the build, read the error and check the dev server itself, instead of pasting output into chat. Works with Claude Desktop (one-click installer), Cursor, Claude Code and Cline. Runs locally over stdio or HTTP, no telemetry. A seatbelt for everyday mistakes, not a sandbox.

Secure agent coding runtime for local Git repos with policy enforcement, RBAC, sessions, approval workflow, and sandboxed writes, optionally connectable to ChatGPT via Secure MCP Tunnel.

Enables a remote Hermes agent to inspect allowed files and propose patch/check requests on a local Git workspace, while the local operator retains approval and applies changes from isolated snapshots.

Safe local MCP server for Windows to list, read, search, patch, backup, and verify code files in allowed folders, with Git integration and dry-run diffs.

A self-hosted MCP server that gives ChatGPT full local machine access for coding tasks, including file editing, shell commands, git operations, and project exploration via 40+ MCP tools.

Enables cross-repository code search over a local mirror of a self-hosted Gitea or Forgejo instance, covering file contents, file paths, and commit messages across all repositories and branches. It also lets users read a single file from the mirror and list mirrored repositories, all without network access during search or read.

Enables ChatGPT to securely operate a single Windows development workspace via a local MCP server, offering file editing, Git status, static analysis, approved test/build, and limited ADB operations with audit logging.

A Windows MCP server for personal Notion Agent integration, providing file read, search, and modification tools in a selected workspace, with an optional trusted developer mode for Python, Git, Node, etc.

A lightweight MCP server that handles git operations on behalf of AI coding assistants, running as a local HTTP service without external network exposure by default.

Enables AI assistants to securely inspect, modify, and manage local projects with trusted filesystem access, safe Git operations, controlled task execution, and developer runtime process management over stdio or HTTP.

Enables ChatGPT web to safely read and modify only explicitly allowed local project files through OpenAI Secure MCP Tunnel, including git operations, file edits, and running project scripts, while enforcing strict security boundaries.

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

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.

Profile-driven MCP server for safely inspecting and changing local Git repositories via a Streamable HTTP endpoint with deny-by-default security.

Clones a Git repo into a temp directory so MCP clients can search and read files from another repo for context.

A secure MCP server that exposes local repository context to ChatGPT/Codex with read-only access, path validation, and no generic shell.

Provides natural language search capabilities for Spryker GitHub repositories, packages, and public documentation. It enables code-level searches across Spryker organizations to help developers find relevant modules and technical information.

Enables ChatGPT Web to inspect a single local workspace read-only via the OpenAI Secure MCP Tunnel, with tools for listing files, reading text, searching, and viewing Git status/diff.

Enables AI assistants to securely inspect local Git repositories and perform restricted write operations in isolated worktrees, with sandboxed script execution and limited GitHub repository management.

An MCP server that enables natural language search capabilities for Spryker packages and code across GitHub repositories, allowing users to find Spryker modules and documentation using conversational queries.

Enables LLMs to perform advanced GitHub code searches with intelligent filtering and content retrieval using Playwright automation, optimized for DeepSeek integration.

Enables Codex and other MCP clients to read kickoff cards, acceptance criteria, Git evidence, and next steps, then append validated, audited progress events for resumable project handoffs.

MCP server for Bitbucket Data Center that enables PR creation, review comment management, and rebasing workflows through natural language commands.

Enables agents to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited progress events with matching Git commits through short-lived scoped credentials.

Self-hosted MCP coding server and unified local Control Center for ChatGPT web, enabling file editing, command execution, Git operations, and optional upstream MCP tools with conversation access controls.

Enables Codex agents to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail and next step, then append validated, audited, idempotent progress events that become matching project-record Git commits. Access is scoped to one workspace and project through short-lived, revocable, hash-stored credentials that cannot touch members, keys, deletion, publication or deployment.