Request path and trust boundaries
End-to-end path
- The AI host (any MCP-capable client—e.g. ChatGPT, Claude, or Agentsyx Agent) talks to the upstream MCP endpoint Agentsyx exposes for your deployment.
- Agentsyx performs authentication, billing / credits, routing, and tool mapping.
- Agentsyx forwards eligible tool calls to your downstream MCP server (and aggregates results back to the host).
Upstream MCP URL shape (Agentsyx)
Agentsyx MCP URL
The canonical production host is https://www.agentsyx.com—always use the www subdomain, not the bare apex domain.
The upstream MCP server endpoint path shape is:
https://www.agentsyx.com/api/v1/flows/[org]/[project]/[deployment]/[connector]/mcpThe exact URL for your connector is shown in Creator. It follows the path shape above; use that value as-is in your MCP client (same host and path as in the UI).
| Segment | Meaning |
|---|---|
[org] | Organization slug |
[project] | Project slug |
[deployment] | Deployment identifier (commonly a UUID) |
[connector] | Upstream connector slug |
Primary JSON-RPC traffic: MCP clients send JSON-RPC over POST to this base URL—the path ends at /mcp with no further segments. Typical methods include initialize, tools/call, and other standard JSON-RPC operations.
Optional path suffixes under /mcp/…: the upstream service may also respond on paths with extra segments for OAuth-protected-resource metadata, OpenID/OAuth discovery (for example under /.well-known/), and some HTTP-oriented aliases such as /mcp/tools for listing tools. Which URLs a client uses is defined by that client or host; consult its documentation if you are wiring a custom integration.
What downstream servers should assume
- Do not treat the downstream URL as a public, self-secured API. Access control and metering are enforced upstream; your server should still validate business rules and secrets for actions that touch external systems.
- Do not re-implement subscription or credit logic in the downstream server unless you have a separate product reason; the platform already gates tool execution upstream.
- Do design tools to be idempotent where possible; retries and duplicate invocations can occur from hosts or proxies.
Trust boundaries
| Layer | Responsibility |
|---|---|
| AI host | Tool selection, user prompts, transport to Agentsyx upstream (third-party hosts or Agentsyx Agent) |
| Agentsyx upstream | Auth, credits, org/project/deployment context, mapping to downstream |
| Downstream MCP | Domain logic, integrations, returning structured tool results |
For concrete headers and argument shapes, see Inputs to downstream servers and Injected parameters & metadata.