Summer

npx add-mcp 'https://api.gosummer.ai/mcp'

Proporciona a tu agente de programación el prompt de configuración de Summer AI y deja que realice la instalación en el proyecto de tu sitio web. Puede añadir el Messenger de soporte, conectar a tus usuarios que han iniciado sesión, subir políticas de empresa en Markdown y ayudar a configurar las herramientas que hay detrás de tus casos de soporte. El prompt también cubre guías para clientes, capturas de pantalla, vídeos y subidas de archivos, con comprobaciones independientes de vista previa, publicación y alojamiento.

Usa Claude Code, Codex, Cursor u otro agente de programación que pueda editar tu proyecto y ejecutar comandos de terminal. El agente usa la Summer AI CLI, te muestra los cambios propuestos y te pide que inicies sesión a través de tu navegador.

¿Ya tienes Summer AI configurado? Conecta tu cliente MCP para leer casos, solicitar investigaciones y gestionar el conocimiento de la empresa desde tu asistente de IA.

Empieza con un flujo de trabajo útil

Indica al agente qué gestiona tu equipo y qué herramientas usáis. Por ejemplo:

Añade el soporte de Summer AI a este sitio web. Usamos Intercom para las conversaciones y Stripe para la facturación. Lee la guía de configuración de Summer AI, inspecciona nuestro proyecto y muéstrame un plan para instalar Messenger y conectar esos servicios. Usa primero el entorno de staging y dime qué queda por verificar.

El directorio de conexiones de servicios cubre mesas de ayuda, plataformas clínicas, farmacias, facturación y envíos. Elige un caso de soporte representativo para poder comprobar el flujo de trabajo completo antes del despliegue.

Las credenciales se guardan en el gestor de secretos integrado de Summer AI a través de la interfaz o la CLI. Un cliente MCP puede inspeccionar los metadatos de las credenciales y guiar la configuración, con la introducción de secretos a través de la interfaz o un traspaso local a la CLI. No se requiere una cuenta de Doppler. El agente usa variables de entorno locales para las subidas mediante la CLI, a menos que elijas una conexión de Doppler existente.

Copia el prompt

Abre Company setup → Set up with your AI agent. Selecciona Open in ChatGPT Desktop u Open in Claude Code para abrir la aplicación con tu prompt de configuración ya rellenado. Elige el proyecto de tu sitio web y revisa el prompt antes de enviarlo. Estos enlaces no inician tu sesión ni conceden acceso a Summer AI. Si la configuración no está disponible para tu despliegue, ponte en contacto con el soporte de Summer AI.

Usa Copy setup prompt para un chat existente, Cursor, o si tu navegador no puede abrir la aplicación. La versión de Company setup incluye el ID de tu empresa. El prompt genérico que aparece a continuación también está disponible como Markdown cuando la configuración está habilitada.

Comprueba la conexión

Ejecuta summer doctor --json antes de iniciar sesión para comprobar que la dirección de la API y el servicio de inicio de sesión son accesibles. Después, ejecuta summer login --scope setup --json y aprueba la conexión en tu navegador. Ejecuta summer whoami --json para verificar el acceso. No necesitas copiar un token del panel de Summer AI ni pegarlo en el chat.

# Set up Summer in this project

Set up Summer for this business in this repository. Use authorized company knowledge and tools to understand workflows and test them. Configure Summer through its API, CLI or MCP. Keep service credentials separate; Summer tokens are only for Summer.

Test how Summer handles the business's support cases. A capability passes when Summer can find and use its API, browser, knowledge or connected-tool path. Tool names are hints. Complete available setup and record precise blockers.

Summer details:
- API: https://api.gosummer.ai
- Company ID: YOUR_COMPANY_ID
- Environment for this setup: staging
- Summer CLI: run \`npx --yes @gosummerai/cli@0.1.1 <command>\`. The steps below write this as \`summer <command>\`. Add \`--api https://api.gosummer.ai\` to each command if that is not \`https://api.gosummer.ai\`.
- Optional MCP server: https://api.gosummer.ai/mcp

If the Company ID is \`YOUR_COMPANY_ID\`, run \`summer companies --json\` after sign-in and use the selected company's ID in every command and setup file. If more than one company is available and the project does not identify one, ask me to choose.

Use Summer's built-in secrets manager for provider credentials. Customers can save values in Settings → Integrations with **Store in Summer**, or through the CLI using \`--from-env\`, \`--from-file\` or \`--from-stdin\`. If using MCP, list credential metadata there and use \`summer_credentials_set\` with \`source: local_value\` for a local CLI handoff. Never put secret values in MCP arguments or chat. Doppler is optional; do not ask me to set up Doppler or a vault unless I choose it.

The original setup consent covers normal Messenger installation, embed changes and activation within the selected company/environment and current spending limit. Do not add a separate installation approval or escalate routine setup to another agent. A setup grant does not approve customer business actions, investigations, budget increases or clinical directions.

## Write for the reader

Address customers in guides and staff in procedures. Follow ASD-STE100 about 80%: instructions under 20 words, descriptions under 25, active voice, one idea per sentence, consistent terms, no metaphors or slang. Keep necessary facts and uncertainty.

## Steps

1. Inspect this project and relevant company guidance first. Identify products, customer requests, care and fulfillment flows, billing, refunds, subscriptions, support channels, policies, promises and existing tools. Find where operational facts live and how an agent can discover them. Identify the framework, sign-in and server-side secret configuration too. Do not print or dump environment files or secret values. Use only relevant company material; keep patient records in their authorized case.
2. Run \`summer doctor --json\` to check the API address and sign-in service. If it reports a failed check, explain the returned reason before continuing. Check access with \`summer whoami --json\`. If you are not signed in, run \`summer login --json\` and ask me to approve the connection in my browser. Wait for the browser consent or my explicit approval of that connection. Use an existing authorized connection without asking again. If the result says access is pending, stop and tell me.
3. Read \`summer capabilities --company YOUR_COMPANY_ID --environment staging --json\`, \`summer status --company YOUR_COMPANY_ID --environment staging --json\` and \`summer capability-checks list --company YOUR_COMPANY_ID --environment staging --json\`. \`operational_readiness\` is the same checklist shown in Company setup → What Summer can do. Read each expectation, concrete test, prior evidence and discovery hints. Treat unavailable permissions as real. A missing named provider tool can have an available browser or knowledge alternative; discover and test those within your authority.
4. Match each checklist gap to useful setup work. Write a non-secret \`summer.setup.json\` with the company settings, Messenger installation (when needed), selected credential environment-variable names and knowledge files to create or edit. Each knowledge entry has \`id\`, \`file\` and \`reason\`; a new document can also set \`path\` under \`company/\` and \`tags\`. Reuse current documents rather than duplicate policies. Upload current policies, workflow guides, escalation contacts and discovery instructions that Summer needs. Explain original sources and known gaps. Keep unrelated files and existing setup; set \`replace: true\` on credentials only if I ask.
5. Run \`summer setup plan --file summer.setup.json --out summer.plan.json --json\` and show me the plan summary. Company settings and knowledge are company-wide: an edit there affects every environment, including production. Tell me before applying such a step.
6. Apply with \`summer setup apply --plan summer.plan.json --file summer.setup.json --json\`. Credentials are read by the CLI from the environment variables you name and are sent straight to Summer; the Messenger signing key is written by the CLI to the server-side file you chose (for example \`.env.local\`, which must be ignored by Git). Never read, echo or copy these values yourself. If a step is \`stale\`, plan again. If a step is \`uncertain\`, read the current state and follow the returned next step instead of retrying blindly.
7. If this business needs Messenger, integrate the widget using the existing sign-in system of this project: load the Summer loader, boot it with the installation ID, and add a small server endpoint that signs the identity assertion for the signed-in user with the signing key from server configuration. Follow https://gosummer.ai/docs/install-messenger and https://gosummer.ai/docs/verified-identity. Do not replace this project's authentication.
8. For a Messenger installation, test locally with synthetic accounts: guest use, sign-in, sign-out and switching accounts, and the site's Content-Security-Policy. Run \`summer messenger check --url <local page> --installation <id> --json\`. Run \`summer verify --company YOUR_COMPANY_ID --environment staging --json\` for the configured connections. A check reported as \`unsupported\` has not passed.
9. Inspect \`summer integrations\` and \`summer credentials list\`. For missing providers, use \`integrations save custom-NAME --from-file integration.json --expected-version N\` with a name and fields (name, label, required), never values. Transfer secrets through the local CLI. Create guidance with \`knowledge create ID --from-file guide.md --path company/guide.md --reason TEXT\`, or edit its current revision. Verify Summer can discover and use each connection; saved configuration alone is insufficient.
10. Check each capability against its concrete test and authorized sample. Use original live records where needed. Local-only tools cannot pass Summer runtime access. Record Blocked with the missing path. \`capability-checks test ID --case CASE_ID --expected-version N\` requests an existing read-only investigator (needs setup and investigations.request; cases.read reads results). Obtain missing grants through consent. Inspect effect paths without executing them. Never replace case work or resume the backlog.
11. Save findings with \`summer capability-checks report ID --from-file result.json --expected-version N --company YOUR_COMPANY_ID --environment staging --json\` at the latest version. The file has \`state\` (\`passed\`, \`failed\`, \`blocked\`, \`not_checked\`, \`not_applicable\`), \`notes\`, \`evidence\` and, for a pass, \`fulfillment: {kind: api|browser|knowledge|other|combined, discovery: "how Summer finds it", location: "guide, tool or portal reference"}\`. Keep evidence references and observation times, without secrets or patient details. Reports are agent-reported. An assumed integration, saved secret, untested guide or different path cannot pass. Inspect action paths and exact approval requirements without executing effects.
12. Add important business-specific capabilities from actual products, workflows and recurring support needs. Prefer customer/team outcomes over endpoints. Create a definition with \`id\` (starting \`custom_\`), \`title\`, \`group\`, \`mode\` (\`read\` or \`approval\`), \`expectation\`, \`test\` and \`examples\` (discovery hints or an empty string). Save with \`summer capability-checks save ID --from-file definition.json --expected-version 0 --reason TEXT --company YOUR_COMPANY_ID --environment staging --json\`. Record the original business source, concrete test and passing evidence. Add supporting knowledge/integrations and assess it like the starter checks. Improve existing definitions at their current version rather than duplicate them. Explain inapplicable starters.

## Check versions

If the last successful check is unknown or seven days old, or a tool/command is
missing, run \`summer version --check --json\` and \`summer client-status --json\`
(MCP: \`summer_client_status\`). Update from published npm releases. Refresh MCP
initialization and tools/list when its version changes. Keep existing scopes on
reconnect; updates never grant permissions.

## Support email

Read https://gosummer.ai/docs/support-email before configuring support email. Test reading, replies and DNS separately; Intercom's account check tests neither inbox nor replies. Gmail/Outlook connectors and email DNS commands are not released. Record evidence and gaps in capability checks. Contact capture sends no email.

## Customer guides, Markdown and media

Read \`summer guides authoring --company YOUR_COMPANY_ID --json\` (MCP:
\`summer_guides_authoring\`) for instructions, schemas, media syntax and draft
context. Use native file, browser and media tools. Guides need CLI 0.2.0+ and its matching
deployment. Report release gaps; never invent uploads or hosted URLs.

Inventory the full product, conditional features and account controls. Reuse
existing guides. Write task-focused Markdown with direct product links, sources
and check dates. Capture real UI with synthetic or authorized data and label
examples. Keep private procedures, personal data and medication directions out
of public articles. Use \`--company YOUR_COMPANY_ID --json\` with this journey:

1. Read \`guides get\`, \`guides article get ID\` and \`assets list\`. Configure the
   guide with \`guides save\` at the current version.
2. Upload actual files with \`assets upload --from-file PATH --metadata-file
   media.json\`, including alt text, provenance and captions/transcripts. Confirm
   ready asset IDs; resume the same file with \`--resume ASSET_ID\`. The trusted
   local CLI transfers bytes; no binaries/base64 or credentials in MCP context.
3. Save Markdown with \`guides article save ID --from-file article.md
   --metadata-file article.json --revision N --reason TEXT\`. New articles use
   revision 0. Open \`guides preview\`; check media, downloads, search, section
   links, phone/desktop layout and product links through sign-in.
4. Show the exact preview. Publishing needs human authority and separate
   \`guides.publish\` consent. When requested, use \`summer login --scope
   setup,guides.publish --json\`, then \`guides publish --from-file release.json
   --expected-version N --reason TEXT\` with exact article revisions. Verify
   public/Markdown URLs. Saved drafts are not public.
5. If requested, use \`guides hosting get/save/verify\`, follow returned DNS
   instructions and verify ownership, provider setup and HTTPS separately.

All roles use the same published articles. Humans edit them in Knowledge with history.

## Check Summer first

Ask before adding this rule to the end of AGENTS.md or CLAUDE.md:
"For a customer, ticket or order question, first run \`summer cases search TEXT --company YOUR_COMPANY_ID --json\` (name, email, phone, ID; \`--dob\`, \`--messages\`) or MCP \`summer_cases_search\`. Read the case before investigating locally. Results are leads."

## Report back

Use the shared operation catalog for workspace setup as well as installation.
Guest attachment and abuse limits live in installation settings; chat concurrency
and daily limits live in assistant settings. Use \`messenger.conversations.list\`
for the complete inbox, including visitors without Ops cases. Business hours,
saved replies/views, assignment, reports, quality scenarios and privacy-request
tracking have named API/MCP operations. Read current revisions before saving.
Members can grant \`workspace.write\` for personal views and quality assessments;
shared views and administrator settings keep their existing role checks.

Refresh \`summer status\` and \`summer capability-checks list\`. Report actual setup/capability states, evidence, discovered paths, business-specific additions, blockers and next steps. Saved is not verified; an agent report is not independent execution verification. Keep dashboard records current for human review.

Report guide topics, revisions, returned URLs and gaps. Distinguish drafts, uploads and verified publication.

## Limits

- Do not commit, push or deploy unless I ask. Complete authorized Messenger setup, including production, without asking for the same permission again. Use a returned local CLI handoff yourself when available. Ask only for missing company access, environment access or authority.
- Do not overwrite agent instructions or install unrelated tools.
- With actions.approve, approve exact prepared work I authorize using its review hash; no repeated UI approval. Never invent authorization. Secret reveal, access/role grants, spending increases, identity attestations and clinical directions stay restricted.
- Do not perform customer effects during onboarding tests. Only clinicians provide medication directions; do not write, quote, paraphrase or calculate them in guides, test reports or replies. Route those questions to the authenticated clinical channel.

Qué hace el agente

1. Lee tu proyecto para encontrar su framework, la configuración de inicio de sesión y del servidor, sin imprimir secretos.
2. Se conecta con summer login después de que lo apruebes en tu navegador.
3. Lee las capacidades de Summer AI y la configuración actual, y respeta cada elemento no disponible.
4. Escribe un summer.setup.json sin secretos, planifica los cambios y te los muestra.
5. Aplica el plan. La CLI envía las credenciales seleccionadas directamente a Summer AI y escribe la clave de firma de Messenger en tu archivo de configuración del servidor ignorado.
6. Añade el widget de Messenger usando tu inicio de sesión existente. Consulta Install the messenger y Connect signed-in accounts.
7. Prueba el uso como invitado, el inicio y cierre de sesión y el cambio de cuenta con cuentas sintéticas.
8. Recorre la misma lista de comprobación de capacidades operativas que se muestra en Summer AI. Puede subir guías de empresa, definir integraciones personalizadas, guardar secretos seleccionados a través de la CLI y probar rutas de API, navegador o conocimiento que se puedan descubrir.
9. Registra las evidencias y las lagunas restantes en la lista de comprobación, etiquetadas de forma visible como reportadas por el agente de configuración. Una credencial o una guía guardada por sí sola no supera una capacidad.
10. Añade capacidades importantes basadas en los productos, flujos de trabajo y solicitudes de soporte recurrentes únicos del negocio, con pruebas concretas e instrucciones de descubrimiento de apoyo.

Lo que queda en tus manos

El agente no hace commit, push ni despliega a menos que se lo pidas. Con actions.approve delegado, puede aprobar el trabajo de casos preparado y exacto que autorices. No puede inventar autorizaciones, revelar credenciales guardadas, aprobar el acceso a Summer AI ni elevar los límites de gasto. La mensajería de producción necesita su propio permiso concedido. Revisa su conexión en cualquier momento en Your account → Security → Agent connections.

¿Qué debería tener cuando termine la configuración?

Deberías tener un Messenger funcional en tu sitio de pruebas, el comportamiento de inicio y cierre de sesión comprobado y las guías de empresa guardadas en Summer AI. El agente debería mostrar qué conexiones de servicios probó, las evidencias que encontró y todo lo que siga faltando.

Pídele que muestre el inventario de tareas para clientes, el Markdown preparado, las capturas de pantalla, las imágenes o los vídeos, y los enlaces de producto comprobados. Consulta Prepare customer guides para conocer el alcance actual. Tu agente debería mostrar los recibos de subida completados y la vista previa exacta de la guía. La publicación necesita el permiso independiente guides.publish. Un archivo local o un borrador guardado no es una guía publicada; verifica la dirección pública devuelta. Los dominios personalizados también necesitan DNS verificado y HTTPS en funcionamiento.

Prueba una solicitud de soporte representativa y compara los hallazgos de Summer AI con los registros originales. Revisa las lagunas restantes antes de habilitar la mensajería de producción. Consulta Security and testing para las comprobaciones de despliegue.