Agent Desktop/Connectors/Install an MCP server from a link
Install an MCP server from a link
Use an Add to Vinkius link to review and add a remote MCP server without placing credentials in the link.
A connector website can offer an Add to Vinkius link. When you select it, Agent Desktop opens a confirmation dialog before adding the remote MCP server.
Add MCP server?
A website requested permission to add this server to Vinkius.
Example MCP
https://example.com
What the link contains
The link identifies the server name and its MCP endpoint. Remote endpoints must use HTTPS. HTTP is accepted only for local loopback addresses such as localhost or 127.0.0.1.
The configuration accepts only the endpoint URL. Do not put API keys, authorization headers, passwords, cookies or environment variables in the link. Links can appear in browser history, system logs or process arguments.
Confirm before adding
The dialog says Add MCP server? and shows the server name and endpoint origin. It warns that the app will discover the server's AI Capabilities after installation but will not run them automatically.
Choose Cancel to dismiss the request. Choose Add MCP server to store the endpoint and begin capability discovery.
After installation
The new connector appears in your connector list. Discovery failure does not silently execute anything. Open the Connector Workspace to retry discovery, configure credentials or review its AI Capabilities.
New capabilities start with the default ask policy. You decide what can run later in Approvals.
Safety limits
The app rejects malformed links, unsupported fields, invalid endpoints, URLs with embedded credentials and links that are too long. Multiple pending requests are queued and duplicate requests are not added twice.