Boilerplate completo para construir soluciones agénticas sobre IBM watsonx Orchestrate (ADK 2.x) con una capa web encima. Destilado de cotemar-poc-n1 y dun-casos-prueba. Incluye: - 11 docs (best practices, architecture patterns, ADK cheatsheet, observability, tool authoring, deployment, RUNBOOK, DEPLOY_TO_NEW_WOX, known-issues con 16 errores reales y fix, eval strategy, INDEX) - 13 templates WxO (orchestrator/specialist/single-meta agents, 3 connections, KB + runbook, observable_tool decorator, coercion helpers, Python tools, OpenAPI spec, backend filter endpoint, webhook validator HMAC, MCP connection) - 6 scripts (deploy idempotente con fallback ADK, undeploy, reset, check-adk-version, new-specialist scaffold, eval-agents runner) - 4 eval pieces (linter de best practices, runner, smoke-test, direct backend probe) + scenario templates - 8 subagentes Claude (.claude/agents/) — wxo-architect, wxo-agent-author, wxo-tool-author, runbook-author, mock-builder, backend-tool-builder, eval-author, web-layer-builder - Skill bundle fit-wxo-bootstrap/ (SKILL.md + 3 templates) listo para copiar a ~/.claude/skills/ - Web layer default FastAPI+HTMX con vista timeline observable + endpoint receptor de trazas - Docker compose Coolify-ready (healthcheck wget -qO-, sin labels Traefik, network split internal:true) - CI Gitea workflow con lint + smoke Best practices enforced por evals/lint_wxo_yaml.py: - A1: máx 10 tools por agente - A3: orchestrator sin tools de remediación - A6: agente sin propósito (react sin tools ni KB) - T1: @observable_tool obligatorio, no @tool directo - T3: _compat shim inline en tools.py - D1: docker-compose sin wget --spider - I-005: OpenAPI con description per-operation - I-009: sin labels Traefik manuales Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
48 lines
1.7 KiB
YAML
48 lines
1.7 KiB
YAML
# ─────────────────────────────────────────────────────────────────────────────
|
|
# Template — Connection MCP (Model Context Protocol)
|
|
#
|
|
# Para sistemas que exponen un MCP server (HubSpot, Outline, GitHub MCP, etc.).
|
|
# ADK descubre las tools del server automáticamente.
|
|
#
|
|
# Setup paso a paso:
|
|
#
|
|
# 1. Importar este YAML:
|
|
# orchestrate connections add -a REPLACE_mcp_name
|
|
#
|
|
# 2. Configurar en draft Y live:
|
|
# for ENV in draft live; do
|
|
# orchestrate connections configure -a REPLACE_mcp_name \
|
|
# --env $ENV --type team --kind mcp
|
|
# orchestrate connections set-credentials -a REPLACE_mcp_name \
|
|
# --env $ENV \
|
|
# -e "MCP_SERVER_URL=https://mi-mcp-server.example.com" \
|
|
# -e "MCP_TOKEN=$MCP_TOKEN"
|
|
# done
|
|
#
|
|
# 3. Listar las tools que ADK descubrió:
|
|
# orchestrate tools list --app-id REPLACE_mcp_name
|
|
#
|
|
# 4. Referenciarlas en el YAML del agente:
|
|
# tools:
|
|
# - REPLACE_mcp_name/get_contact
|
|
# - REPLACE_mcp_name/create_deal
|
|
# ─────────────────────────────────────────────────────────────────────────────
|
|
|
|
spec_version: v1
|
|
kind: connection
|
|
name: REPLACE_mcp_name
|
|
display_name: "REPLACE — MCP server"
|
|
description: |
|
|
Connection MCP a REPLACE_SISTEMA.
|
|
Tools descubiertas automáticamente del server.
|
|
schema_version: "1.0"
|
|
|
|
auth_type: mcp
|
|
identifier: REPLACE_mcp_name_conn
|
|
|
|
preference:
|
|
- environment: draft
|
|
schema_id: mcp
|
|
- environment: live
|
|
schema_id: mcp
|