Most apps accept the Workleap Agent as soon as you click Connect. A few only allow sign-in from apps that an admin of that tool registered first. This page gives the values to enter. The registration is the same for an app in your Connected apps list and for a custom MCP server your Workleap admin added.
When you need this
The app's row in Personal integrations says so
You click Connect, sign in, and the connection fails right after
You are adding a custom MCP server and see "The MCP server's authorization server supports neither dynamic client registration nor client-id metadata documents"
The tool's documentation says AI agents or MCP clients must be registered by an admin
What to enter
Every tool's form is different. These are the answers to the fields they have in common.
Field | What to enter |
Name of the app or integration | Workleap Agent |
Redirect URI or callback URL | Both of these: |
Access type or authorization context | Personal or user-level. Each person signs in with their own account. |
Registration type or client type | Automatic, if offered. Otherwise the tool issues a Client ID, and sometimes a Client secret. Copy both. |
Scopes or permissions | The ones the tool documents for its MCP server |
Grant type | Authorization code, with refresh token |
PKCE | Required |
Important: add both redirect URIs. Workleap has two places to connect from, and each one uses a different URI.
After registering
For an app in your Connected apps list, there is nothing more to do in Workleap. Everyone in your organization can now click Connect on that app.
For a custom MCP server, give the Client ID and Client secret to your Workleap admin. They enter them when they add the server. See Connect a custom MCP server. If the tool offered automatic registration, those two fields stay empty.