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 Yaver MCP server?
Phone-first local dev MCP for Claude Code and Codex: install Yaver, pair mobile, run, build, deploy.
How to install Yaver
Copy-paste configuration for popular MCP clients.
YAVER_HEADLESSSet to 1 to force device-code OAuth instead of opening a browser (useful in remote / WSL / sandboxed environments).
{
"mcpServers": {
"yaver": {
"command": "npx",
"args": [
"-y",
"yaver-cli"
],
"env": {
"YAVER_HEADLESS": "<YOUR_YAVER_HEADLESS>"
}
}
}
}Related MCP servers
Linux package, file, command, vulnerability, lifecycle, migration, and repository intelligence.
View repository →
Polis Protocol
Local-first control plane for coding agents: routing, reservations, and guardrails.
MCP server for 1C: Platform Tools, enabling AI agents to run tests, build configurations, and manage 1C databases.

md-feedback
Review markdown plans before AI agents build. Annotate, gate-check, apply fixes, session handoffs.

io.github.yb48666-ctrl/otr-protocol
Merchant trust verification for AI agents. One call = trust score, badge, and purchase safety.
Your Team0 AI Chief of Staff, reachable from any agent — answers, acts, and coordinates.

