coding-agent-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@coding-agent-mcpshow git status for the current project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Agent MCP
Agent MCP is a containerized Model Context Protocol (MCP) server for coding agents. It exposes a project-oriented toolset for file editing, shell commands, long-running process management, Git helpers, HTTP fetches, browser inspection with Playwright, package installation, and project snapshots.
The server is implemented with FastMCP and runs over streamable HTTP at /mcp.
Features
Open and switch between host project directories.
Read, write, append, patch, move, copy, delete, and search files.
Run one-off shell commands with timeouts.
Start, inspect, wait on, stop, and forget long-running background processes.
Inspect Git status, diffs, logs, branches, checkout, and commit local changes.
Fetch URLs from inside the container.
Run browser automation with Playwright Chromium.
Capture DOM, accessibility, form, network, storage, console, and error snapshots.
Keep persistent browser sessions across multiple MCP calls.
Create, restore, and list local project snapshots.
Install Debian, Python, and Node packages in the running container.
Report environment and project metadata.
Related MCP server: Containerized Strands Agents
Repository Layout
.
├── app/
│ ├── __init__.py
│ └── server.py
├── Dockerfile
├── docker-compose.yml
├── requirements.txt
└── README.mdRequirements
For Docker usage:
Docker
Docker Compose
For local Python usage:
Python 3.12 or newer
pipPlaywright browser dependencies
Docker is the recommended way to run this project because the image installs the tools the MCP server exposes to agents, including Git, Docker CLI, Node, npm, pnpm, Yarn, Go, Rust, Java, ripgrep, SQLite, PostgreSQL client tools, and Chromium for Playwright.
Quick Start
Build and run the MCP server:
docker compose up --buildThe compose file maps the MCP server to:
http://localhost:8081/mcpThe container listens on port 8080; the host mapping is 8081:8080.
MCP Client Configuration
Use a streamable HTTP MCP connection pointed at:
http://localhost:8081/mcpThe server name is:
coding-agent-mcpExact MCP client configuration differs by client. Use streamable HTTP as the transport and the URL above as the endpoint.
Docker Compose Details
The included docker-compose.yml starts one service named mcp-server.
Important mounts:
/home/anshagrawal:/hostexposes the host workspace tree inside the container../app:/app/appenables live editing of the server source while developing../snapshots:/snapshotsstores project snapshots outside the container./var/run/docker.sock:/var/run/docker.socklets tools inside the container talk to the host Docker daemon./home/anshagrawal/.ssh:/root/.ssh:roexposes SSH credentials read-only for Git operations.
Important environment values:
HOME=/hostmakes agent shell commands use the mounted host tree as home.PLAYWRIGHT_BROWSERS_PATH=/ms-playwrightuses the Chromium install baked into the image.GIT_SSH_COMMANDselects the mounted SSH key and accepts new host keys.NO_PROXY/no_proxykeep localhost and host gateway traffic local.
If you use this project on another machine, update the host-specific paths in docker-compose.yml before running it.
Local Development
Create and activate a virtual environment:
python -m venv .venv
source .venv/bin/activateInstall dependencies:
pip install -r requirements.txt
python -m playwright install --with-deps chromiumRun the server locally:
python -m app.serverBy default, the server binds to 0.0.0.0:8080 and serves MCP traffic at /mcp.
Tool Groups
Project Tools
open_projectswitch_projectlist_projectsclose_projectpwdget_project_infoenvironment_info
File and Search Tools
write_fileappend_fileread_fileread_filesreplace_in_filereplace_linesinsert_at_linecopy_pathmove_pathdelete_pathcreate_directorylist_filestreefind_filesearch_filesregex_searchfind_symbolstat_pathapply_patch
Shell and Process Tools
run_commandcommand_historystart_processlist_processesget_process_outputwait_for_process_outputstop_processforget_process
Git Tools
git_statusgit_diffgit_loggit_branchgit_checkoutgit_commit
Browser Tools
browser_inspectbrowser_check_errorsbrowser_interactbrowser_evaluatebrowser_dom_snapshotbrowser_accessibility_snapshotbrowser_form_snapshotbrowser_assertbrowser_network_tracebrowser_storage_statebrowser_session_openbrowser_session_listbrowser_session_closebrowser_session_inspectbrowser_session_interactbrowser_session_evaluatebrowser_session_dom_snapshotbrowser_session_accessibility_snapshotbrowser_session_logs
Snapshot Tools
create_snapshotrestore_snapshotlist_snapshots
Dependency Tools
install_apt_packagesinstall_python_packagesinstall_node_packagesinstall_project_dependencies
Browser Action Format
Browser interaction tools accept action dictionaries. Locator fields can use one of:
selectorrolewith optionalnametextlabelplaceholdertest_idalt_texttitle
Supported actions include:
clickdblclickfilltypepresshovercheckuncheckselectfocusblurwait_for_selectorwait_for_textwait_for_urlwaitgotoreloadassert_textassert_selectorassert_countassert_urlassert_titleevaluate
Example action payload:
[
{
"action": "fill",
"label": "Search",
"value": "agent mcp"
},
{
"action": "press",
"label": "Search",
"value": "Enter"
},
{
"action": "assert_text",
"text": "Results"
}
]Snapshots
Snapshots are stored under /snapshots in the container and mapped to ./snapshots by Docker Compose. A snapshot copies the active project while ignoring common generated directories such as .git, node_modules, __pycache__, .venv, dist, and build.
Security Notes
This server is intentionally powerful. It can read and write mounted files, run shell commands, install packages, access the Docker socket, use mounted SSH credentials, and automate browsers. Run it only in trusted environments and expose the MCP endpoint only to trusted clients.
Review the host paths in docker-compose.yml before sharing or deploying this project. The defaults are tailored to the original development machine and may expose more of the host filesystem than you want.
Configuration
Most behavior is currently configured in app/server.py:
HOST_ROOT=/hostSNAPSHOT_ROOT=/snapshotsPROCESS_LOG_LIMIT=5000BROWSER_LOG_LIMIT=500MAX_READ_BYTES=500000MAX_OUTPUT=80000DEFAULT_TIMEOUT_SECONDS=30
The Docker image sets:
PYTHONDONTWRITEBYTECODE=1PYTHONUNBUFFERED=1PLAYWRIGHT_BROWSERS_PATH=/ms-playwright
Development Workflow
Useful checks:
python -m compileall appRun the container:
docker compose up --buildCheck the exposed endpoint from the host:
curl http://localhost:8081/mcpThe MCP endpoint may return a protocol-specific response depending on the request; this command is primarily a connectivity check.
License
No license file is included yet. Add one before publishing this project for reuse by other people or organizations.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/spyduck007/agent-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server