Multi-connector architecture
Recommended split
For maintainability and blast-radius control, prefer multiple downstream MCP servers rather than one monolith:
| Role | Examples | Notes |
|---|---|---|
| UI / widgets | OpenAI Apps SDK MCP, static resource servers | Frequent UI iteration; keep tools narrow |
| Core backend | Your domain API MCP | Business logic, persistence |
| Integrations | Zapier, n8n, Make MCP bridges | Isolate third-party credentials and quotas |
Practices
- Least privilege — Integration connectors should expose only the automations needed for mapped tools.
- Failure isolation — A broken Zap should not take down core read-only tools.
- Naming — Use clear connector and tool names in Creator so mappings stay understandable.
- Idempotency — Automation backends may retry; design tools so repeated calls are safe or deduplicated.
See also Integration platforms.