Cclarity Linkedin Mcp
@get-cclarity
CClarity connects AI assistants (Claude, ChatGPT, Cursor, etc.) to your LinkedIn world inside the CClarity platform: profile and business context, ICP, writing style, post analytics, profile viewers, outbound engagement history, inbound “who engaged” on your posts, connection inv
Overview
What is Cclarity Linkedin Mcp?
Cclarity Linkedin Mcp connects AI assistants (such as Claude, ChatGPT, and Cursor) to your LinkedIn world through the CClarity platform. It provides access to profile context, business context, ideal customer profile (ICP), writing style, post analytics, profile viewers, outbound engagement history, inbound “who engaged” on your posts, connection invitations, and followers.
How to use Cclarity Linkedin Mcp?
The server runs remotely at https://api.cclarity.io via Streamable HTTP. End users typically connect through the published stdio bridge package @cclarity-packages/mcp, which uses browser OAuth and a local proxy.
Key features of Cclarity Linkedin Mcp
- Profile and business context from LinkedIn
- Ideal Customer Profile (ICP) data
- Writing style analysis
- Post analytics and engagement metrics
- Profile viewers list
- Outbound engagement history
- Inbound “who engaged” on posts
- Connection invitations management
- Followers data
Use cases of Cclarity Linkedin Mcp
- Enrich an AI assistant with personalized LinkedIn context for sales outreach
- Analyze post performance and audience engagement
- Manage connection requests and follower insights
- Tailor communication style based on historical LinkedIn activity
- Track who viewed your LinkedIn profile
FAQ from Cclarity Linkedin Mcp
What AI assistants are supported?
Cclarity Linkedin Mcp works with Claude, ChatGPT, Cursor, and other AI assistants that support the Model Context Protocol.
How do I connect to the Cclarity Linkedin Mcp server?
You can connect either directly via the remote MCP endpoint at https://api.cclarity.io (Streamable HTTP) or by using the stdio bridge package @cclarity-packages/mcp, which handles browser OAuth and local proxy connection.
What data can I access through this server?
The server provides profile context, business context, ICP, writing style, post analytics, profile viewers, outbound engagement history, inbound engagement (who engaged on your posts), connection invitations, and followers.
Is authentication required?
Yes, the stdio bridge uses browser OAuth for authentication. When using the remote HTTP endpoint, authentication details are not specified in the README but are likely required.
