Agentic Developer MCP Server
An MCP server implementation that clones a Git repository and runs Codex on its contents.
Overview
This MCP server provides a tool for cloning a Git repository, optionally checking out a specific branch, focusing on a particular folder, and running Codex with a given request.
Installation
# Install the package in development mode
pip install -e .
Usage
You can run the MCP server using either stdio or SSE transport:
# Using stdio (default)
python -m mcp_server
# Using SSE on a specific port
python -m mcp_server --transport sse --port 8000
Tool Documentation
run_codex
Clones a repository, checks out a specific branch (optional), navigates to a specific folder (optional), and runs Codex with the given request.
Parameters
repository(required): Git repository URLbranch(optional): Git branch to checkoutfolder(optional): Folder within the repository to focus onrequest(required): Codex request/prompt to run
Example
{
"repository": "https://github.com/username/repo.git",
"branch": "main",
"folder": "src",
"request": "Analyze this code and suggest improvements"
}
Development
This project uses the MCP Python SDK to implement an MCP server. The primary implementation is in mcp_server/server.py.
License
MIT
Metadata
Release files for iflow-mcp_teabranch-agentic_developer 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_teabranch_agentic_developer-0.1.0.tar.gz | 5.5 kB | Without provenance | Details for iflow_mcp_teabranch_agentic_developer-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_teabranch_agentic_developer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_teabranch_agentic_developer-0.1.0-py3-none-any.whl |
Total release size: 11.6 kB
Release files / iflow_mcp_teabranch_agentic_developer-0.1.0.tar.gz
| Download URL | iflow_mcp_teabranch_agentic_developer-0.1.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf33b3adefc570116bcd4285dcd21aeb6518d44e824dc7a420e05e78c601b5e2
|
|
BLAKE2b-256 checksum How to use checksums |
81b823e9c9c390e67fd39b244f4d84c7cd66bc7e687b889dcee8256045458fc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.2 {"installer":{"name":"uv","version":"0.10.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_teabranch_agentic_developer-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_teabranch_agentic_developer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de9044811c825c4f1e62379c74654091b33f75f676179eef36695b4f93232d70
|
|
BLAKE2b-256 checksum How to use checksums |
4279da346d9e2946894e6d4b5233e60e3cbdb8219c883a3578bd5c40d3a51d68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.2 {"installer":{"name":"uv","version":"0.10.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_teabranch-agentic_developer 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.