list_connectors
List the Connectors Marketplace — every connector Subscriby knows, lane by lane, with its badges, manifest and the form that connects it.
Answer "which connectors exist, which can a creator install today, and what does each do?". Every card carries its lane (status: available, beta, paused, in_development, coming_soon), whether it is installable, whether it is official, its badges (official or community, new, trending), the category, tagline, overview and links, and, for a connector that exists as a package, the whole manifest: install_mode, scopes, the resource_kinds it gates with their grant mode, capabilities, messaging limits, pacing, the management_commands its in-chat surface renders and the missing_commands it does not, relay_modes, the recovery facets, and the declarative install_fields and settings_fields a client renders as the connect form. The payload is exactly what GET /v1/connectors returns; the same document is the subscriby://connectors/catalog resource.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Annotations
It reads and never changes anything.
Arguments
statusstringoptionalNarrow to one lane: `available`, `beta`, `paused`, `in_development` or `coming_soon`. Omit for every lane.
availablebetapausedin_developmentcoming_soonWhat it returns
{ "data": [ { "key": "telegram", "name": "Telegram", "vendor": "Subscriby", "version": "1.0.0", "status": "available", "status_label": "Available Now", "installable": true, "official": true, "badges": [{ "key": "official", "label": "Official" }], "category": "messaging", "tagline": "Sell access to Telegram channels, groups and supergroups through your own bot.", "install_mode": "paste_credential", "scopes": ["project", "platform"], "resource_kinds": [ { "kind": "channel", "label": "Channel", "portal_label": "Channel", "icon": "megaphone", "grant_mode": "bearer_link", "supports_early_admission_hold": true, "upgrades_from": null, "plan_kinds": ["one_time", "recurring", "pass", "pass_series"] } ], "capabilities": ["messaging", "access_control", "management_surface"], "install_fields": [ { "name": "token", "type": "secret", "label": "Bot token", "required": true, "rules": ["string"], "steps": [], "links": {} } ] }, { "key": "slack", "name": "Slack", "status": "coming_soon", "status_label": "Coming Soon", "installable": false, "badges": [], "eta": "Planned", "install_mode": null, "resource_kinds": [], "install_fields": [] } ], "meta": { "total": 5 }}Cards come installable lanes first, then by name. See the Connectors API for every lane, badge and manifest key.
How it fails
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks project-connector:view-any.
VALIDATION_FAILEDstatus names no lane; context.accepted lists them.
How is this guide?
Last updated on
list_connector_installations
List every connector installation a project holds — live and standby — with its state, health and the platform's own account for it.
restore_connector_access
Bring a project's detached places on a reinstalled connector back and hand every live purchase of a plan granting them fresh access.