A connector to a personal network is a standing risk, and the useful question is how quickly you can cut it. Being able to revoke from LinkedIn itself — not only from the vendor's dashboard — means you are not dependent on the intermediary staying reachable. The setup is as light as it gets: browser authorisation, nothing to paste.
Cclarity's endpoint for reaching LinkedIn from an MCP client. Their setup guides are written for Claude specifically, and the connection is established entirely through the browser.
LinkedIn access through their service. The endpoint requires authorisation before listing anything, so the surface here is what Cclarity documents.
OAuth 2.0 with PKCE and dynamic client registration — the vendor points out there is no client id or secret to enter, scope mcp:tools. Access can be revoked from LinkedIn's own settings or the Cclarity dashboard, and takes effect immediately.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen