Call connections.probe_connector_address
Check how a member's own MCP server or API address wants to sign in, before they set it up — 'check this API address before I add it', 'does this connector need a token'. Ask a member's own MCP server or API address how it signs in, BEFORE they set it up. Use it when the operator says they want to bring their own connector and gives you an address: it dials the address once, reads nothing but the way it refuses, and reports whether it wants a token, a sign-in with the provider, or nothing at all. It writes no row, stores no credential and registers nothing — finishing the setup is the operator's own act in Connections → Add custom connector, because the token they may need to paste is a value no tool may ever carry. Not for refreshing a connector already set up — that is connections.resync_custom_connector.
Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/connections.probe_connector_address
- Auth: HTTP bearer
Headers
Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.
Request body
Response
The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.
Changes
No recorded changes to this operation across all 6 revisions of this API.