AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
MCP verified MIT Self-run

Aws Bedrock Ops Agent

mcp-h-vance-aws-bedrock-ops-agent · by h-vance

L2 triage copilot for support engineers: ingests incident evidence bundles and returns ranked hypotheses, checks, and escalation notes over both REST and MCP.

No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add mcp-h-vance-aws-bedrock-ops-agent

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access Used
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/mcp-h-vance-aws-bedrock-ops-agent)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude DesktopCursorWindsurf

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Aws Bedrock Ops Agent? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

AWS Bedrock Agent

[](https://aws-bedrock-ops-agent.onrender.com) [](https://render.com/deploy) [](https://fastapi.tiangolo.com) [](https://python.org)

> L2 triage copilot for support engineers: ingests incident evidence bundles and returns hypotheses, checks, and escalation-ready notes, not a general chat assistant.

Part of the Ops Support Demo portfolio.

Overview

A structured triage copilot that consumes incident evidence bundles and returns ranked hypotheses, recommended checks, and escalation documentation. Designed for support engineers who need AI assistance grounded in actual incident data, not open-ended conversation.

Features

  • Structured Triage: POST /triage accepts an incident evidence bundle; returns JSON with hypotheses, checks, and escalation readiness.
  • MCP Server: the same triage logic is exposed as an MCP tool at /mcp, so any MCP-aware client (n8n, a custom agent, etc.) can call it directly. See [MCP Server docs](docs/MCP_SERVER.md).
  • Mock Mode: BEDROCK_MOCK=true returns deterministic canned responses that work offline with no AWS credentials.
  • Live Bedrock Mode: BEDROCK_MOCK=false invokes Amazon Bedrock Runtime with validated structured output.

Documentation

  • [Architecture](docs/ARCHITECTURE.md) - system boundaries, request flow, modes, and known limits
  • [MCP Server](docs/MCP_SERVER.md) - the /mcp tool surface, transport, and how to connect a client
  • [n8n Workflow](docs/N8N_WORKFLOW.md) - webhook → triage → Slack automation, ready to import
  • [Operations Runbook](docs/RUNBOOK.md) - health checks, local/Render operations, failures, and rollback
  • [Security Notes](docs/SECURITY.md) - data handling, access controls, model output safety, and review checklist
  • [Portfolio Review Guide](docs/PORTFOLIO_REVIEW.md) - suggested reviewer path, tradeoffs, and discussion topics

Quickstart

# Install runtime dependencies
pip install -r requirements.txt

# Start with mock mode (no AWS needed)
BEDROCK_MOCK=true python assistant.py

API

POST /triage

Request: incident evidence bundle

{
  "incident_id": "INC-001",
  "summary": "Auth cascade after token rotation",
  "timeline": [
    { "ts": "2025-01-15T10:00:00Z", "event": "...", "trace_id": "tx-001" }
  ],
  "log_lines": [
    { "level": "error", "message": "...", "trace_id": "tx-001" }
  ],
  "request_samples": [
    { "method": "GET", "path": "/api/v1/data", "status": 403 }
  ],
  "related_endpoints": ["/login", "/api/v1/data"]
}

Response: structured triage output

{
  "incident_id": "INC-001",
  "hypotheses": [
    {
      "rank": 1,
      "hypothesis": "Token rotation invalidated active sessions without grace period",
      "confidence": "high",
      "evidence_ids": ["tx-001"],
      "check_command": "curl -s -H 'Authorization: Bearer ' http://localhost:8000/api/v1/data"
    }
  ],
  "recommended_checks": [
    "Verify token expiry on /login response",
    "Check if /api/v1/data accepts the new token format"
  ],
  "escalation_ready": true,
  "customer_comms_draft": "We identified an authentication failure caused by a token rotation that invalidated active sessions. Engineering is reviewing the rollout sequence."
}

Environment Variables

| Variable | Default | Description | |----------|---------|-------------| | BEDROCK_MOCK | true | Use canned responses (no AWS) or call Bedrock | | LAB_BASE_URL | http://failure-lab:8000 | Used in /health response to indicate connected lab | | CORS_ORIGINS | http://localhost:8080,http://127.0.0.1:8080 | Comma-separated browser origins allowed to call the API | | AWS_REGION | us-east-1 | AWS region for Bedrock runtime calls | | BEDROCK_MODEL_ID | amazon.titan-text-express-v1 | Bedrock model invoked in live mode | | MCP_ALLOWED_HOSTS | 127.0.0.1:*,localhost:*,[::1]:* | Comma-separated Host header allowlist for the /mcp endpoint | | MCP_ALLOWED_ORIGINS | http://127.0.0.1:*,http://localhost:*,http://[::1]:* | Comma-separated Origin header allowlist for the /mcp endpoint | | RATE_LIMIT_REQUESTS | 20 | Max requests per client IP per window on /triage and /mcp | | RATE_LIMIT_WINDOW_SECONDS | 3600 | Rate limit window, in seconds | | LANGFUSE_PUBLIC_KEY / LANGFUSE_SECRET_KEY | unset | Enables OTel tracing of Bedrock calls to Langfuse when both are set; no-op otherwise | | LANGFUSE_HOST | https://us.cloud.langfuse.com | Langfuse region endpoint |

Note: CORS is pre-configured to accept requests from http://localhost:8080 and http://127.0.0.1:8080 (the debug console). For production, set CORS_ORIGINS to the deployed browser origin. /mcp has its own separate Host/Origin allowlist. See [docs/MCPSERVER.md](docs/MCPSERVER.md).

Endpoints

| Method | Path | Description | |--------|------|-------------| | GET | /health | Returns status, mode (mock/live), and lab_url | | POST | /triage | Accepts evidence bundle; returns hypotheses, checks, escalation notes | | POST | /mcp/ | MCP streamable-HTTP endpoint exposing the triage_incident tool. See [docs/MCPSERVER.md](docs/MCPSERVER.md) |

Deployment

Live Demo (Render)

curl https://aws-bedrock-ops-agent.onrender.com/health
curl -X POST https://aws-bedrock-ops-agent.onrender.com/triage \
  -H "Content-Type: application/json" \
  -d '{"incident_id":"INC-001","summary":"Auth cascade after token rotation","timeline":[],"log_lines":[],"request_samples":[],"related_endpoints":[]}'

The live demo runs on Render's free tier with BEDROCK_MOCK=true. No AWS credentials needed.

Local (Mock)

BEDROCK_MOCK=true python assistant.py

CORS

The FastAPI app includes pre-configured CORSMiddleware allowing http://localhost:8080 and http://127.0.0.1:8080 (the debug console). Set CORS_ORIGINS when deploying under a custom domain.

Development

pip install -r requirements-dev.txt
ruff check .
pytest

Security

Use least-privilege AWS credentials for live Bedrock mode. Keep the public demo in mock mode unless authentication, rate limiting, and stricter observability are added.

Related

License

MIT

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.