Sociavault
olamide-olaniyanLABSCO SUMMARY
Two independent revocation paths is the right property for anything holding a social account.
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.
What it is
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.
What you get
LinkedIn access through Cclarity's service.
Requirements
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.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Reaching LinkedIn from an assistant
Authorise once in the browser rather than handling API credentials.
02
Cutting access quickly
Revoke from LinkedIn's own settings or the vendor dashboard; either takes effect immediately.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.0 with PKCE and dynamic client registration, scope mcp:tools — the vendor notes there is no client ID or secret to supply
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://api.cclarity.io/mcpRequirements
- OAuth 2.0 with PKCE and dynamic client registration, scope mcp:tools — the vendor notes there is no client ID or secret to supply
