If a tool your team uses has an MCP server, or you built one for an internal system, an organization admin can register it in Workleap. The Workleap Agent can then use its tools, and each person signs in to that server with their own account.
Prerequisites
Requirement | How to check |
A public HTTPS address | It starts with https:// and works from outside your company network. VPN-only and localhost addresses cannot be registered. |
Sign-in with OAuth | The server sends users to a sign-in page. A server that wants an API key pasted in does not qualify. |
A Client ID and Client secret, sometimes | Only if the server does not register apps automatically. Its documentation says so and provides them. See Register the Workleap Agent in another tool. Members never need them. |
How it works
An admin registers the server with its address, a Display name, and a Description the agent will read. For example: "Our support ticket system. Use it for questions about tickets, incidents, and on-call."
Workleap checks that the server answers over HTTPS and offers OAuth sign-in before saving it.
Each person connects once, with their own account on that server.
When a question matches the description, the agent uses the server's tools as that person. Ask "Which tickets are open for my team?" and it answers with what your account can see.
Setup
Admins: register the server
Only organization admins can open the agent settings. Anyone else sees a page-not-found error.
Open the agent settings and go to Custom MCP servers.
Click Add server.
Enter the Server URL, a Display name, and a Description.
Enter the Client ID and Client secret only if the tool gave you them. The secret is not shown again after saving.
Click Save. The check takes a few seconds. The server then appears in the list.
Everyone: connect your account
Open Connected apps from your account settings. The server is listed under the Display name your admin gave it. In the agent, you can also find it under Sources.
Click Connect and sign in to the tool.
The agent can use the server from your next message.
If the tool asks you to create an app first
Some tools do not register apps automatically. Their documentation asks you to create an app, an integration, or a client, and asks for a Redirect URI. Use the values in Register the Workleap Agent in another tool. If the tool then gives you a Client ID and a Client secret, enter them when you add the server.
Good to know
Up to 25 servers per organization, and up to 50 tools from each.
Registering the same address twice creates duplicate tools. Remove the extra one.
To change a Client secret, remove the server and add it back.
Removing a server disconnects everyone in Workleap. It does not revoke access on the tool's side.
Troubleshooting
Message | What to do |
The MCP server could not be reached at a public https address, or it does not implement the MCP authorization specification. | Confirm the address is public, answers over HTTPS within 10 seconds, and offers OAuth sign-in. The tool's support team can confirm the last one. |
The MCP server's authorization server supports neither dynamic client registration nor client-id metadata documents. | Register the Workleap Agent with the tool to get a Client ID, then add the server again with it. See Register the Workleap Agent in another tool. |
You have reached the maximum number of servers. | Remove a server you no longer use. |
The Custom MCP servers section is missing. | Only organization admins see it. Ask an admin to register the server. |