get_connector
Read one Connectors Marketplace card by key — its lane, badges and, for a connector that exists as a package, its manifest and the form that connects it.
Answer "what can this connector do?" or "what does connecting it ask the creator for?" for one connector. The card is the same list_connectors returns: status and installable, official and the badges, the category, tagline, overview and links, and for a registered connector the manifest with its resource_kinds, capabilities, messaging limits, pacing, management_commands and missing_commands, recovery facets and the declarative install_fields and settings_fields. A roadmap entry (coming_soon) answers too, with every manifest key null or empty. The REST twin is GET /v1/connectors/{key}.
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
connector*stringThe connector key, as `list_connectors` returns it.
What 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.", "links": { "documentation": "https://docs.subscriby.net/connectors/telegram", "support": "mailto:support@subscriby.net", "privacy": "https://telegram.org/privacy", "terms": "https://telegram.org/tos", "homepage": "https://telegram.org" }, "added_at": "2025-04-21", "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 } ], "capabilities": [ "messaging", "access_control", "management_surface", "recovery_probes" ], "messaging": { "max_length": 4096, "buttons_per_row": 8, "max_buttons": 100, "callback_data_bytes": 64, "supports_underline": true, "supports_spoiler": true, "supports_files": true }, "pacing": { "min_interval_microseconds": 35000, "burst": 30, "per_recipient_interval_microseconds": 1000000 }, "management_commands": ["project_create", "plan_manage"], "missing_commands": ["creator_tasks"], "recovery": { "probes": true, "standby_installations": true, "resource_standby": false, "mirror": false, "identity_relink": false }, "install_fields": [ { "name": "token", "type": "secret", "label": "Bot token", "help": "Paste the token @BotFather gave you.", "required": true, "rules": ["string"], "options": [], "value": null, "steps": [], "links": {} } ], "settings_fields": [] }, "meta": {}}How it fails
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks project-connector:view-any.
RESOURCE_NOT_FOUNDno connector is known by that key; context.connector echoes it.
How is this guide?
Last updated on
disconnect_connector
Disconnect a project's installation of one connector — the connector withdraws it, the credentials are wiped, the row stays. Destructive.
get_connector_installation
Read a project's live installation of one connector — its state, health and the platform's own account for it — and learn why it is missing when it is.