MCP Architecture Canvas
Haz clic en cada bloque para expandirlo · Auto-guardado activado
0 / 6 blocks completed
① Context — Who and why
★ 1 · Agente Host
🤖 What agent consumes these servers?
Define the host or client that will initiate MCP connections.
Host MCP
Alcance de los servidores
★ 2 · Architecture Decision
🧭 ¿Por qué MCP? ¿Qué granularidad?
The most important decision: what to hardcode and what to expose as a standalone MCP server.
Why MCP instead of hardcoded tools?
Estrategia de granularidad
Build vs Buy
② Design — What servers to build
3 · Inventario de Servidores MCP
🗂️ What servers will you build or integrate?
Define each server with its purpose, what it exposes, and how it runs. Tools are actions (possible side effects); Resources are readable data (URI).
③ Implementation — How to connect and secure
4 · Transporte & Runtime
🔌 How does the client connect to the server?
Protocolo de transporte
stdio
Proceso local (stdio)
The host launches the server as a subprocess. Maximum privacy. Ideal for local tools and development.
SSE / HTTP
Servidor remoto (SSE)
The server runs as a standalone HTTP process. Allows sharing across multiple clients and cloud deployment.
Runtime environment
Ciclo de vida del servidor
5 · Seguridad & Auth
🔐 Who can call what?
Authentication mechanism
Permissions by operation type
Sandboxing del servidor
Datos sensibles en tools
④ Operaciones — Testing, despliegue y observabilidad
6 · Testing, Despliegue & Observabilidad
🧪 ¿Cómo verificar que los servidores funcionan?
Testing
CI/CD
Observabilidad
Versioning & distribution
🎉 Canvas MCP completado
Design ready to review with your team or export as a document.