MCP server for AWS Elastic Beanstalk: read the fleet; --allow-writes adds two-phase writes.
MCPpedia last refreshed this data
io.github.tombaldwin/ebman is an MCP server that MCP server for AWS Elastic Beanstalk: read the fleet; --allow-writes adds two-phase writes. Its tool list has not been published yet over stdio, requires no API key, and scores 37/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-tombaldwin-ebman": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A k9s-style TUI for AWS Elastic Beanstalk. Triage red envs, stream logs, edit option settings, deploy new versions — all from the keyboard. If you've used k9s with Kubernetes, the muscle memory carries: : for commands, / to filter, Enter to drill in, ? for context-aware help.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud
MCP Server for GCP environment for interacting with various Observability APIs.
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
Azure DevOps boards, repos, pipelines & projects for AI agents — governed.
Manage BlazingCDN from AI agents: CDN zones, cache, metrics, domains, cloud storage and video CDN
MCP Security Weekly
Get CVE alerts and security updates for io.github.tombaldwin/ebman and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A k9s-style TUI for AWS Elastic Beanstalk. Triage red envs, stream logs, edit option settings, deploy new versions — all from the keyboard. If you've used k9s with Kubernetes, the muscle memory carries: : for commands, / to filter, Enter to drill in, ? for context-aware help.
Install · Quickstart · Triage workflow · Highlights · Why ebman? · Docs

Captured from
ebman --demo, the synthetic-fleet mode that ships with the binary. Regenerate the gif withvhs demo.tapeafter a code change.
Homebrew (macOS / Linux):
brew install tombaldwin/tap/ebman
Cargo:
cargo install ebman
Pre-built binary: download the tarball for your platform from the GitHub Releases page, verify the *.sha256 next to it, extract, and put ebman on your PATH.
Tested on Rust 1.91+. macOS (Apple Silicon + Intel) and Linux x86_64. AWS SDK uses the standard credentials chain (AWS_PROFILE / AWS_REGION env, ~/.aws/credentials, instance role, etc.).
For the prettier glyph set (Powerline pill chain, Nerd Font tab icons), see docs/fonts.md. The default icons = "unicode" works fine in any terminal.
ebman # launch the TUI
ebman --read-only # disable all write surfaces (audit-friendly)
ebman --demo # synthetic fleet (no AWS calls) — for screenshots / VHS
ebman --version
ebman --help
Once running, press ? for a per-context keymap (Detail, DLQ, Action menu, Saved-configs overlay all have scoped help).
Production env goes red at 3am. From your terminal:
ebman — launch; prod-api shows up tinted red in the table/prod-api ↵ — jump to it! — open :why: recent events / alarms / instance health / last deploys, all in one overlay:diff prod-api staging-api — confirm staging is still on the previous version:rollback — redeploy the last-known-good version label, with a 5-second undo window~/.cache/ebman/audit.logFive keystrokes to triage, one command to fix. The AWS-console alternative is a minimum of five page-loads, two tabs, and zero audit trail.
Built for operators who triage EB envs daily and don't want the AWS console round-trip — or the eb deploy ; aws elasticbeanstalk describe-events --max-items 50 | jq ... shell-pipeline every time something goes red.
:why opens a one-screen diagnostic: recent events + alarms + instance health + last deploys, with a DLQ peek for Worker envs.:incident START "headline" freezes deploys fleet-wide, pins a header banner with a running clock, and audit-logs the window; :event-tail streams EB events across every env in one overlay; ebman audit replay <line-id> re-runs an audited action for post