Busabase para AWS Quick

Conectar AWS Quick a Busabase

AWS's AI assistant for work (launched as Amazon Quick, renamed AWS Quick on 2026-11-09): a chat agent on web, desktop and mobile that automates tasks, analyses data, builds web apps and runs research across connected files, email, calendar, CRM and databases. Free and Plus plans need no AWS account; an Enterprise subscription unlocks team connectors, including custom MCP integrations.

Servidor MCP de Busabase

https://busabase.com/api/mcp

Leer la documentación de AWS Quick
Busabase
Conector MCP
Una Base de publicaciones en un espacio de trabajo de Busabase, con registros, vistas y prompts para agentes

Configúralo

El chat alojado no tiene shell ni sistema de archivos, así que un conector es la vía de entrada.

Añade el servidor

Apunta tu cliente de chat al endpoint MCP de Busabase.

Inicia sesión

Completa OAuth en el navegador — no hay que crear ningún id ni secreto de cliente.

Elige el permiso mínimo

changeRequest permite al agente proponer pero nunca fusionar.

Verifica

Pide al agente que llame a auth_verify antes de hacer cualquier trabajo.

Para este agente

AWS Quick documents Agent Skills on the desktop app: a skill is a folder with a SKILL.md file at its root, created under Customize > Skills (from chat, from a .md/.zip file, or from a folder), and loaded with progressive disclosure — name and description first, full instructions on activation. Because Quick has no general shell, skills there package instructions for Quick itself rather than running the Busabase SETUP_SKILL.md install flow; use the MCP connector to connect Busabase.

Paso a paso

Este cliente no tiene shell, así que un conector es la única vía de entrada.

De un vistazo

Proveedor
Amazon Web Services (AWS)
Cómo se conecta
MCP + OAuth
Transporte
HTTP en streaming
Autenticación
OAuth (registro dinámico)

AWS Quick has no shell of its own, so connect Busabase as a remote MCP connector (this needs an AWS Quick Enterprise subscription):

  1. Sign in to AWS Quick and open Connectors.
  2. Open the Create for your team tab and choose Model Context Protocol (MCP).
  3. Name the integration Busabase, enter https://busabase.com/api/mcp as the MCP server endpoint, and choose Public network as the connection type. Choose Next.
  4. Select User authentication (OAuth). Busabase supports Dynamic Client Registration, so Quick discovers the authorization server from Busabase's protected-resource metadata and registers itself automatically — no client ID or secret to paste. Complete the Busabase sign-in and consent in the browser.
  5. Choose Create and continue, review the tools Quick discovered (each MCP tool registers as a Quick action), and share the integration with your team if needed.

After that, ask Quick to use a Busabase action in chat — for example, to list your spaces or read a Base — to confirm the connection works.

Problemas conocidos

Remote servers only — local stdio connections are not supported, and HTTP streaming is preferred over SSE. The MCP integration requires an AWS Quick Enterprise subscription. Custom MCP connectors do not sync automatically: the owner must open the connector and choose Sync, and custom connectors that use a VPC connection cannot sync at all (delete and recreate to refresh tools). A sync re-runs authorization — if Busabase later requires OAuth scopes that were not granted originally, the sync fails until you re-authorize. During creation Quick validates every tool's inputSchema against JSON Schema Draft 7 or later; tools using deprecated Draft 3 syntax fail publishing with "Creation failed". Quick also documents Agent Skills (folders with a SKILL.md at the root, created under Customize > Skills), but with no shell surface the MCP connector above is the route that connects Busabase.

Cómo se compara

Capacidades de conexión, lado a lado con otros agentes ya presentes en este directorio.

CapacidadAWS QuickClaude CodeCursor
TipoApps de escritorioAgentes de terminalEditores con IA
Camino recomendadoConector MCPHabilidad del agenteHabilidad del agente
Cómo se conectaMCP + OAuthMCP + OAuth · Complemento / HabilidadMCP + OAuth · Complemento / Habilidad
TransporteHTTP en streamingHTTP en streamingHTTP en streaming
AutenticaciónOAuth (registro dinámico)OAuth (registro dinámico)OAuth (registro dinámico)
Estos pasosDe la documentación oficialÚltima comprobación 11 nov 2026

Escritos a partir de la propia documentación de este agente. No hemos vuelto a ejecutar cada paso en una máquina real, así que revisa la documentación enlazada si algún comando ha cambiado.

Deja que tu agente haga la configuración

Una sola instrucción, una autorización, y cada cambio que haga después lleva un mensaje y un diff que puedes revisar o revertir.

Ver todos los agentes

Servidor MCP de Busabase

https://busabase.com/api/mcp