Connection types
| Type | Discovery | Description |
|---|---|---|
mcp | Automatic | Model Context Protocol server. Tools are discovered via tools/list. |
rest | Manual | REST API endpoint. Tools defined manually. |
graphql | Manual | GraphQL endpoint. |
database | Manual | Direct database connection. |
MCP transports
MCP connections support two transports:HTTP (Streamable HTTP)
The MCP server runs as an HTTP service. SupaProxy connects to its URL and calls tools via HTTP requests.STDIO
The MCP server runs as a subprocess. SupaProxy spawns the process and communicates via stdin/stdout.Tool discovery
When a connection is saved (HTTP) or first queried (STDIO), SupaProxy calls the MCP server’stools/list endpoint. Each tool has:
- Name: unique identifier (e.g.
get_order_status) - Description: what the tool does
- Input schema: JSON Schema for the tool’s parameters
- Is write: whether the tool modifies data (triggers write confirmation guardrail)
The agent loop
When a query arrives:- SupaProxy connects to all workspace MCP servers
- Discovers available tools from each connection
- Sends the query, system prompt, and tool definitions to the language model
- The model returns tool call requests
- SupaProxy executes each tool call against the correct connection
- Results are fed back to the model
- Repeat until the model returns a final text answer
Connection status
| Status | Meaning |
|---|---|
connected | Connection is healthy and tools are available |
disconnected | Connection has not been verified or is offline |
error | Last connection attempt failed |