"Creating files in Xcode development environment" matching MCP servers:

A modular monolith MCP server connecting multiple providers (Redash, PostgreSQL, GitHub) with unified permission, security, and auditing, enabling secure data access and tool execution.

Centralized MCP server that provides standardized development workflow commands to Cursor AI, auto-detecting project type (Laravel, Next.js, Flutter, Architecture) and offering relevant commands for implementation, testing, and commits.

An MCP server that enforces development discipline and workflow best practices, guiding users through a structured process of coding, testing, documenting, committing, and releasing.

A Model Context Protocol server that enables Claude to manage software development projects with complete context awareness and code execution through Docker environments.

Integrates Zoho Projects, Git, and SonarQube to automate task management, branch creation, code quality checks, and reporting for React developers.

Deployable MCP server for GitHub and Vercel integration. Enables creating repos, pushing multiple files in a single commit, deploying projects to Vercel, managing environment variables, and combined deploy workflows via natural language.

Enables read-only access to the canonical-vault GitHub repository through MCP, letting clients list files, retrieve file contents and history, inspect commits, and search code.

Provides MCP tools to get a single-call snapshot of git and GitHub Actions CI status across all repositories in a folder, flag missing or stale architecture docs, write doc files, and detect release drift between source and release repositories.

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

Enables AI coding agents to orchestrate the full software development lifecycle on GitHub, including planning, issue creation, code review, security triage, and release readiness checks.

An MCP server for creating, validating, and formatting Git commits with emojis following the conventional commit standard.

A Model Context Protocol server that enables AI assistants to interact with Azure DevOps services, allowing users to query work items with plans to support creating/updating items, managing pipelines, handling pull requests, and administering sprints and branch policies.

Governance and session management layer for AI-assisted software development; enables agent binding, session tracking, and structured code review within the HestAI ecosystem.

An MCP server that provides deterministic tools for AI assistants to standardize development workflows, including branch naming, commit validation, and PR checklists.

MCP server for creating, versioning, retrieving, and publishing HTML presentations, using git as the source of truth and Google Apps Script for deployment.

Fetches glasz-style spec files (product.md, tech.md, test-plan.md, and INDEX.md) from GitHub repositories, enabling LLMs to answer questions about features, stories, and acceptance criteria without cloning or pasting files.

An MCP server that enables AI assistants to interact with GitHub via a fine-grained personal access token — pushing commits, managing branches, opening and merging PRs, creating issues, and reading repositories. It runs locally with no telemetry and supports a read-only mode.

Quilt gives every AI agent line-level authorship in a shared Git checkout, so multiple agents work in one repo, and each commits only its own lines, with symbol-level claims that block collisions before any bytes change.

Repository-native protocol and MCP server for coordinating work items, documentation, changelogs, and project memory between humans and AI agents, using Markdown files in a Git repository as the canonical data source.

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