What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the dev.yafl/mcp MCP server?
Agent-first E2EE file transfer over MCP: move files between machines in one tool call, gone in 24h.
How to install dev.yafl/mcp
Copy-paste configuration for popular MCP clients.
YAFL_API_KEYsecretAPI key for authenticated transfers. Optional — omit and run `yafl login` (device flow) instead.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@yafldev/mcp"
],
"env": {
"YAFL_API_KEY": "<YOUR_YAFL_API_KEY>"
}
}
}
}Related MCP servers
deploy the software your AI builds you

ZopDev MCP
Cloud cost, inventory and governance on AWS/Azure/GCP. Read-only by default, optional scoped writes
Deploy, monitor, and manage your OpenClaw AI assistants via natural language.
Disposable test mailboxes on a real domain: send, receive and assert on real email.
View repository →Trust Layer for AI work. Give your AI hands. Every run returns a verifiable receipt. No key needed.
View repository →Agent utility belt: memory, locks, webhook inboxes, timers, DNS, email, URL, timezone, cron
