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 secret, sometimes | Only if the server does not register apps automatically. The vendor's documentation says so and provides them. Members never need them. |
How it works
An admin registers the server with its address, a 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
Open Workleap AI Settings and go to the Custom MCP servers section.
Click Add server.
Enter the Server URL, a Display name, and the Description.
Enter the Client ID and Client secret only if the vendor 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 the agent, find the server under Sources, click Connect, and sign in with the vendor. The agent can use the server from your next message.
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 secret, remove the server and add it back.
Removing a server disconnects everyone in Workleap. It does not revoke access on the vendor'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 vendor can confirm the last one. |
The MCP server's authorization server supports neither dynamic client registration nor client-id metadata documents. | Get a Client ID from the vendor and try again. |
You have reached the maximum number of servers. | Remove a server you no longer use. |
The Custom MCP servers section is missing. | You are not an organization admin, or the feature is not available on your account yet. Contact your account representative. |
