PDM

Connecting an agent ​

For an AI assistant to work with PDM it has to be set up once: add PDM to its list of external tools and approve the access in a browser. No password goes into the settings — you type it only on the ordinary PDM sign-in page.

What you will need ​

  • An AI client with MCP support. MCP is the common protocol AI assistants use to plug in external tools. Claude Code and Claude Desktop support it, for example; any application able to connect to remote MCP servers over HTTP will do.
  • The PDM account you normally work under, plus permissions on the stands you need. There is no such thing as a separate "agent account".
  • The connection is made to the PDM MCP server — a separate address that acts as an adapter between the AI client and PDM. It has no users and no data of its own.

Step 1. Add PDM to your client's settings ​

Add PDM to your client's list of MCP servers (where that list lives is described in the client's own documentation):

json
{
  "mcpServers": {
    "pdm": {
      "url": "https://mcp.pdm.iappx.com/mcp"
    }
  }
}

Here pdm is simply the connection name the server will appear under in the client; rename it if you like. The address needs no changes: it is already filled in for this PDM installation.

If your client uses a different settings format

Some clients ask not for a file but for two fields: a connection type and an address. In that case pick a remote HTTP connection and enter the same address as in the example above. There should be no tokens, logins or passwords in the settings.

Once the settings are saved, restart the AI client if it does not do so itself.

Step 2. Approve access in the browser ​

On its first call to PDM the client will report that authorization is required and open a browser.

  1. If you are not signed in to PDM yet, the usual sign-in screen appears — enter your corporate login and password (see Signing in).
  2. On the “Account access” page, check the “Application” and “Permissions” fields: once you approve, that application will be able to act in PDM in your name.
  3. Click “Allow” — the browser returns you to the AI client and the connection starts working.

If access was denied, you can try again at any point — just call PDM from the AI client once more.

The password is never passed to the agent

This is the standard access-approval mechanism: you type the password only on the PDM sign-in page, while the application receives time-limited access bound to a separate session. If specific permissions were named in the request, the agent's access is narrowed further — it is not a way to widen your own permissions.

You do not have to approve access again on every launch: as long as the session is not ended, the client connects by itself.

Step 3. Check that it works ​

Ask the assistant a simple read-only question — to list the stands, say, or to report the status of one particular stand. If the answer contains stand names you recognise, the connection is set up.

How to revoke access ​

A connected application occupies a separate session tagged “Agent”; end it in the account settings — the revocation takes effect immediately, access does not linger "until the end of the day". To connect again you will have to go through the approval in step 2 once more. See Active sessions for details.

Revoke access if you connected the agent for a one-off task, worked from a shared or borrowed computer, or no longer use that application.

If the connection does not work ​

What you seeWhat to check
The client does not list PDM among its toolsThe settings were saved in the wrong place, or the client was not restarted. Check the client's documentation and restart it
The browser did not open and authorization never startedLaunch the AI client so that it has access to a browser, or open the link it offers manually
The approval page says the authorization request is invalidThe link was opened incomplete or has expired. Close the page and call PDM from the AI client again
Access approved, but the agent replies that there is no dataMost likely permissions are missing. Check whether you see the same thing in the PDM interface and contact an administrator if needed
The agent could see data and now asks for authorization againThe agent's session was ended in the account settings — including by revoking all sessions at once. Approve access once more
An error in an operation that involves GitLabThe “GitLab token” field is empty in your profile — see Account settings

If none of the above helps, contact an administrator: the MCP server's address and availability are their responsibility.

See also ​