well_show_connector_request

io.github.WellApp-ai/well-mcp · Verify this server

Show the person a card for ONE tool Well cannot connect yet: the card names the tool, says where it stands in words (under maintenance, coming soon, not offered, or not in Well), and, except for a tool under maintenance, offers a request button, which asks Well to add it. Never name the button's label: the card writes it in the person's language. Call it when the person names one tool to connect and a well_list_connectors read with that tool's `slug` (then `q`) returned no connectable row. Pass the name as the person wrote it, and the slug when a read returned one. Never offer another tool in its place, and never say Well refuses it. When `status` comes back "available", the tool can be connected now: draw the connect card with well_list_connectors and the `slug` of this result instead, and say nothing about a request. When `connected` is true, the workspace already holds a connection to the tool: no request card is drawn, so say in one line that it is already connected, and offer no request. When `requested` is true, say the workspace already asked for it. When `can_add_self` is true, the card also offers "Ajouter moi-même": its click comes back as the person's next message, and the add-custom-connector skill adds the tool by the address of its MCP server. When it is false, never offer to add the tool oneself. Write one line for the person, then stop: the card's button records the request and its click comes back as the person's next message. When no card is drawn and the person asks for the tool in words, call well_request_connector with the same name. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.