PluginBench
MCP Server

Yeku MCP Server

dev.yeku/yeku

Registry
How to choose

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 Yeku MCP server?

deploy the software your AI builds you

How to install Yeku

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "yeku": {
      "url": "https://mcp.yeku.dev/mcp"
    }
  }
}

Related MCP servers

ZOZopDev MCP logo

Cloud cost, inventory and governance on AWS/Azure/GCP. Read-only by default, optional scoped writes

0
Apache-2.0
View repository →

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 →

88 free engineering calculators: RF link budgets, LoRa/Meshtastic, PCB, solar, homelab. Keyless.

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