Test and share the wrapped endpoint
Verify a Gooshi-wrapped MCP connection before giving it to users.
The wrapped endpoint is the client-facing MCP address managed from Gooshi. Test it with every MCP client type you intend to support.
Why testing matters
Discovery proves that Gooshi can inspect the upstream MCP. It does not prove that an AI client can discover the wrapped tools, send a call through Gooshi, receive the upstream result, and create an Activity event. Establish that baseline before adding a trigger so client setup, upstream, trigger, and payment problems do not look the same.
Test checklist
- Open the MCP server's Test section.
- Copy the wrapped endpoint.
- Add it to a compatible MCP client as a remote MCP connection.
- Start a clean client session.
- Call a discovered tool with safe input.
- Confirm the expected result in the client.
- Confirm the call appears in Activity.
Choose Refresh test status after the call. Activity also refreshes every five seconds while its page is open and provides a Refresh now control.
Client setup
Always paste the wrapped Gooshi endpoint shown in Test, not the upstream MCP URL.
ChatGPT
- Open Settings → Security and login and enable Developer mode.
- Open ChatGPT Plugins, choose +, and add a URL connection using the wrapped endpoint.
- Start a new chat, enable the connection, and request one safe discovered tool action.
Claude
- Open Customize → Connectors.
- Choose + → Add custom connector and paste the wrapped endpoint.
- Enable the connector in a new conversation and request one safe tool action.
Cursor
Add a remote Streamable HTTP MCP server in Cursor's MCP settings using the wrapped endpoint, then start a new Agent chat and request one safe tool action.
Codex
Open Settings → MCP servers → Add server, choose Streamable HTTP, and
paste the wrapped endpoint. Save and restart Codex, confirm the server with
/mcp, then request one safe tool action.
Menu names and availability can vary by plan and client version. If the exact label differs, look for a remote connector or Streamable HTTP MCP server.
If payments are enabled, also test a tool call that should remain available and one that should require payment. Payment UI and automatic continuation depend on calling-client capabilities. Use ChatGPT for Gooshi's current complete payment acceptance test: trigger the gate, complete sandbox payment, confirm the original tool and exact arguments resume, and verify one completion in Activity.
Before sharing
- Confirm the endpoint belongs to the intended MCP server.
- Confirm recent upstream changes are reflected in Tools.
- Review published triggers and prices.
- Record which MCP clients you tested.
Client behavior can differ, so a successful test in one client does not automatically qualify every other client.