OpenAI Responses
A remote MCP tool in the Responses API, with the approval card in front of anything that writes.
The Responses API takes a remote MCP server as a tool. The model gets your bindings; your keys stay in the vault and the writes still stop for a person.
Connect it
{
"type": "mcp",
"server_label": "sallyport",
"server_url": "https://mcp.sallyport.cloud/mcp",
"headers": { "Authorization": "Bearer sp_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }
}Approvals in a server-side loop
A backend loop has no browser to open, so the gateway answers with a call id, an approval URL and an expected wait. Surface the URL to whoever owns the action, and repeat the call with the id once it is answered. The operation continues instead of starting again.
Field names come from the vendor. `sp init --client openai-responses` prints the current shape for the version you are on.