Turn the MCP connector on or off for your organization.
The per-firm switch the MCP auth path checks on every request.
Without this endpoint the self-service flow did not actually work: absence of a settings row means DISABLED, nothing else created one, so a firm could mint a key and get 401 the MCP connector is not enabled for this organization with no way to fix it from the dashboard.
Disabling does NOT revoke keys. That separation is the point — an operator can suspend a firm without invalidating credentials their team has already deployed into infrastructure we do not control, and re-enabling restores service without a re-integration.
Returns the full connection state so the settings page re-renders from one round trip rather than toggling and then re-fetching.
Request
- Base URLhttps://api.signalshq.io (the document declares no server; this is the origin it was published from)
- AuthOAuth 2PasswordToken URL: /auth/login
Request body
Example request
{
"rate_limit_per_minute": 60,
"daily_spend_cap_cents": 5000
}Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.