Connect AI apps

You can connect Claude, ChatGPT, Cursor, Codex or any other AI client that speaks MCP to VentionDesk yourself — without an API key. The app signs in through your VentionDesk account, and when connecting you decide what it may do. This works for owners and staff members; customer accounts of the customer portal cannot connect an AI app.

The page for international users and app directories, with the list of all tools and example prompts: Connect AI apps to VentionDesk.

How a connection works

1. Enter the URL. In the AI app, add an MCP server (often called “connector” or “integration”) with this URL: https://api.ventiondesk.com/mcp. The app needs nothing else — it finds the way to the sign-in on its own.
2. Sign in. The app opens a browser window with the VentionDesk sign-in. If you are already signed in, it continues directly.
3. Consent. VentionDesk shows a consent page with the app’s name (under /oauth/zustimmen). There you choose:
   • the workspace, if you belong to more than one,
   • the permissions — as a staff member only those the owner has released for AI apps,
   • the projects — all (including future ones) or a selection.
4. Connected. After your consent you return to the app. From now on it works with exactly these permissions — not with your own. If you decline, the connection is aborted without anything being stored.

The app gets the same tools as an agent key (see Claude and MCP); what a tool may do is determined by the permissions you chose. What the app reads goes to its provider — for example Anthropic, OpenAI or Anysphere. Whether your workspace may do that is its own decision; for tickets, customer data and times with names you usually need a data processing agreement with the provider.

Claude

claude.ai and Claude Desktop: Under Settings › Connectors add a custom connector, with “VentionDesk” as the name and https://api.ventiondesk.com/mcp as the URL. Then “Connect” — sign-in and consent follow as above. Whether custom connectors are enabled in your plan and organisation is decided by Anthropic or your Claude administrator.

Claude Code: in the terminal

claude mcp add --transport http ventiondesk https://api.ventiondesk.com/mcp

and then call /mcp in Claude Code and sign in to “ventiondesk”. If you prefer working with a fixed key, follow Claude and MCP.

Working through tasks like with /aufgaben — also in the app without a file system: “Work on the next open VentionDesk task”. Claude claims the next task by the same rule as the task runner, reads the description, history and project, fetches screenshots only when needed, reports the result with evidence and closes the run. For this the connection needs the permissions of the “Claude runner” template (read and report tasks, manage runs, read projects).

ChatGPT

In the settings under Connectors (depending on the version “Apps & Connectors”; custom MCP servers require developer mode), create a new connector: URL https://api.ventiondesk.com/mcp, authentication OAuth. Sign-in and consent follow on first use. Which plans allow custom connectors is decided by OpenAI.

Cursor

In ~/.cursor/mcp.json (for all projects) or .cursor/mcp.json (this project only):

{
  "mcpServers": {
    "ventiondesk": {
      "url": "https://api.ventiondesk.com/mcp"
    }
  }
}

Cursor then shows the server under Settings › MCP with a sign-in notice; a click on it starts sign-in and consent.

Codex

In ~/.codex/config.toml:

[mcp_servers.ventiondesk]
url = "https://api.ventiondesk.com/mcp"

Then codex mcp login ventiondesk — the browser opens sign-in and consent. Older versions of Codex only speak MCP over HTTP with an additional switch; if in doubt, check the help of your Codex version.

Other clients

Every client that supports MCP over HTTP (“Streamable HTTP”) with OAuth finds the way itself: to a request without sign-in, https://api.ventiondesk.com/mcp answers with 401 and points to https://api.ventiondesk.com/.well-known/oauth-protected-resource; that is where VentionDesk’s sign-in service is listed. The client registers itself there — there is nothing you need to create beforehand.

The OAuth scopes a client requests (openid, email, profile) only concern the sign-in. What the app may do in VentionDesk is chosen on the consent page.

Disconnecting and expiry

Under Settings › My AI apps you see your connections in all workspaces: app, permissions, projects, connected on and last used. “Disconnect” ends a connection immediately — a sign-in the app has already been issued is no longer valid afterwards either. For your own connection, VentionDesk also withdraws the approval at sign-in; if you connect the app again, VentionDesk asks you again.

A connection that has not been used for 90 days ends on its own. Simply connect the app again when you need it.

As the owner you also see the connections of all people in your workspace there and can disconnect any of them. You also decide which permissions staff members may give an AI app. By default these are the permissions of the templates “Read only” and “Claude runner” — read projects, tasks and deployments, report on tasks and record runs —, nothing sensitive. You yourself may grant every permission except recording access, which only the operator may do. If you narrow the release, it applies to existing connections from the app’s next token — usually within an hour.

Every connection and every disconnect appears in your workspace’s log; changes an app makes appear there as far as VentionDesk logs them — each with app and person, for example “AI app: Claude · Anna Schmidt”.

AI app or API key?