What AI assistants are supported?
Cclarity Linkedin Mcp works with Claude, ChatGPT, Cursor, and other AI assistants that support the Model Context Protocol.
@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
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"cclarity": {
"command": "npx",
"args": [
"-y",
"@cclarity-packages/mcp",
"cclarity-mcp"
],
"env": {
"CCLARITY_MCP_URL": "https://api.cclarity.io"
}
}
}
}Authenticate with CClarity. Opens a browser window to complete sign-in, payment, and LinkedIn (Unipile) connection. Token is saved locally for all subsequent calls. Call this first — no arguments needed.
Logout from CClarity and clear all locally stored credentials.
Check CClarity authentication status and server connectivity. Shows login state, token expiry, and number of available upstream tools.
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.
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.
Cclarity Linkedin Mcp works with Claude, ChatGPT, Cursor, and other AI assistants that support the Model Context Protocol.
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.
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.
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.

Docs: https://botchelor.com/agents and https://botchelor.com/llms.txt . Botchelor is a blind-date show for fictional characters, and AI agents are welcome to play. Over MCP, your agent builds an original character in w
Model Context Protocol (MCP) server for Hostinger API. If you don't want to install or run anything locally, connect directly to Hostinger's hosted MCP server: This opens a browser window to authorize via OAuth. Once app

scvd.store is an evidence observatory for agentic commerce. Independent signed observation of what other people's endpoints, artifacts and payments actually did among other things. USDC on Base, Arbitrum One, World Chain
28-tool MCP server for web scraping, crawling, deep research & autonomous extraction — clean Markdown & structured JSON for Claude, Cursor & any MCP client. 1,000 free one-time credits, local-Ollama LLM support.
Official MCP server for BlazingCDN - AI agents (Claude, Cursor, Windsurf) manage CDN resources, purge cache, query metrics, domains, Anycast CDN, Video CDN and Media CDN
コメント