MCP Integration Reference

This section is a formal reference for downstream MCP server implementers: what reaches your server, what Agentsyx injects, and how to structure multi-server apps. It is not a walkthrough of the Agentsyx Creator UI.

For conceptual background, see What is MCP?.

In this reference

• Request path & trust boundaries — Who calls whom; what you must not re-implement.
• Inputs to downstream servers — Messages, arguments, headers, correlation.
• Injected parameters & metadata — Platform-added fields (verify names against current apps/saas-starter when integrating).
• Anonymous & unauthenticated users — Behavior when identity is limited or absent.
• MCP server metadata — Discovery, serverInfo, tool listings.
• MCP App (widgets) metadata — UI resources, host–widget contracts.
• Multi-connector architecture — Splitting UI, core tools, and integrations.
• Integration platforms — Zapier, n8n, Make patterns.
• Versioning & compatibility — Avoiding breaking upstream mappings.
• Troubleshooting — Common failure modes and what to log.

Implementation details are grounded in monorepo/apps/saas-starter; if this doc and code disagree, trust the code and open an issue on the docs repo.