Niches · Code & developer platforms
Commit and push from a sandbox or CI run without a browser
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
The commit lands on a branch on the host from the headless environment using an environment-variable token, with the token scoped to the one repository, and the run exits with the commit SHA in its output.
How agents ask for it: commit this and push a branch
, run this agent in a container with repo access
, stage and commit the change
, authenticate the agent to the host from CI
Does the job, with a limit 5
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Entire BB Entire Inc | ENTIRE_TOKEN takes a service-account secret the CLI exchanges and renews, grants scope the account to one repository; but a login token expires after 8 hours, and clones need the git-remote-entire helper rather than plain HTTPS. source |
| Git (MCP reference server) C Model Context Protocol, a Series of LF Projects, LLC | git_add and git_commit return the new commit hash, --repository confines the server and hooks and core.fsmonitor no longer run since v2.4.0; but there is no push, fetch or remote operation, so another tool must land the commit on the host. source |
| GitHub MCP Server BB GitHub, Inc. | create_or_update_file and push_files commit through the API with a fine-grained PAT from an environment variable, and v2.1.0 ships Linux binaries so no Docker is needed; but one account found fine-grained tokens too coarse and an earlier Kubernetes deploy failed on the Docker image. source |
| GitLab MCP Server B GitLab Inc. | add_commit commits file actions through the API with a fine-grained PAT from the environment, so no git or Docker is needed; whether that token can be confined to one project is not stated. source |
| graft C Vishisht Choudhary (individual) | gft write --parent --land commits without a checkout, GFT_TOKEN carries a policy token, and /v1/refs/update returns 412 on a stale old value; but the server speaks plain HTTP with no TLS and the author field is whatever the client sends. source |
Doesn't do this job 16
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| amCharts 5 MCP Server B amCharts | No git or host tools. |
| Azure DevOps MCP Server B Microsoft Corporation | No commit or push tool; repo_file is read-only and the server does not run git. source |
| Context7 BB Upstash | No git or host tools. |
| GitMCP E Ido Salomon (GitMCP open-source project) | No git or write tools. |
| Graphify BB Graphify Labs | No git or host tools. |
| Jam MCP C Jam | No git tools. |
| Microsoft Learn MCP Server D Microsoft Corporation | No git tools. |
| ModusToolbox AI Assistant D Infineon Technologies AG | No git tools. |
| Momentic MCP server D Momentic | No git tools. |
| REA BB morluto | No git tools. |
| Ref D Ref Software, Inc | No git tools. |
| Salesforce DX MCP Server C Salesforce, Inc. | commit_devops_center_work_item commits within DevOps Center only; no general git or token route. |
| Sourcegraph MCP Server B Sourcegraph, Inc. | No git or write tools. |
| Superpowers B Prime Radiant (no legal form or registration found on its pages); the MIT LICENSE names Jesse Vincent | No git tool; commits come from the harness. |
| TokenEconomizer B Microsoft Corporation (repository in the microsoft GitHub organisation with Microsoft's SECURITY.md); co-authors at UC Berkeley | No git tools. |
| Void B Cloudflare, Inc. (VoidZero) | Deploys code; it does not commit or push. |
What stops agents finishing
- server shipped only as a Docker image and the pod cannot run Docker
- OAuth with dynamic client registration and no token route (remote Azure DevOps for Claude Code and Codex)
- fine-grained tokens still cannot scope to one operation
- read-only git tools ran repository hooks and core.fsmonitor until November 2026 (CVE-2026-41903)
Around it
Before: code.ticket-to-pr, agent-harnesses.embed-in-program. After: code.review-pr, code.host-ops.
Where this comes from
Weight 8 of 100 in Code & developer platforms: 6 of 65 accounts (K8s deploy failure, agent gateway for sandbox calls, container loop with gh, fine-grained token limits, Twill.ai switch to gh, git reference server advisory)
The same as data: /api/v1/use-cases/code.commit-from-sandbox.json, or the MCP tool get_use_case with id code.commit-from-sandbox. Other jobs in this category: /api/v1/niches?category=code.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.