Add the server URL
In your MCP client, add Queber as a remote server at https://mcp.queber.app/mcp.
Queber exposes the same desktop automation capabilities through two integration surfaces: MCP for MCP-capable clients and REST API Actions for HTTPS integrations.
MCP clients connect directly to the remote MCP endpoint and speak the MCP protocol. Access is granted per user through OAuth and works only while your Queber Desktop app is online.
In your MCP client, add Queber as a remote server at https://mcp.queber.app/mcp.
The client opens an OAuth approval screen where you review the app and requested permissions.
Queber Desktop connects to the MCP server in the background. Tools work only while your signed-in desktop app is online.
Most clients register themselves. If yours asks for a client id and secret, create an OAuth app in the Queber member area and paste its credentials and redirect URI.
Your MCP client calls the Queber remote MCP endpoint with its access token.
Queber validates the token, paid-plan access, and required MCP scopes.
The server relays the command to your signed-in Queber Desktop app over its secure background connection.
The client receives structured status, profile, job, or automation output from the desktop app.
See whether your desktop relay is connected and which capabilities are available.
List profiles, inspect one profile, open it manually, or close local sessions.
List jobs, read logs, check progress, cancel pending or running jobs, and retry failed jobs.
Create immediate or scheduled jobs for supported platforms and automation types.
Access is controlled by OAuth tokens, requested scopes, paid-plan checks, and the live Queber Desktop connection. Revoke a client if you no longer trust it.