linkedin — agdata MCP Tool
linkedin
(linkedin) is one of 31 tools on the
agdata
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call linkedin from your client
- Claude Code agdata linkedin run in your project directory
- Claude Desktop agdata linkedin ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agdata linkedin ~/.cursor/mcp.json
- VS Code agdata linkedin .vscode/mcp.json
- Zed agdata linkedin ~/.config/zed/settings.json
- Windsurf agdata linkedin ~/.codeium/windsurf/mcp_config.json
- Cline agdata linkedin ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agdata linkedin ~/.gemini/settings.json
- Grok agdata linkedin .mcp.json (in your project root)
- ChatGPT agdata linkedin Settings → Connectors → Advanced → Developer mode
- Claude.ai agdata linkedin Settings → Connectors → Add custom connector
- LangChain agdata linkedin pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agdata https://agdata.shveik.dev/mcpOther tools on this server
- unblock
- google-maps
- tiktok
- youtube
- amazon
- google-search
- google-maps-reviews
- youtube-transcript
- screenshot
- linkedin-jobs
- indeed-jobs
- shopify-products
- google-news
- amazon-reviews
- google-play-reviews
- linkedin-company
- web-search
- x-replies
- youtube-comments
- tiktok-comments
- instagram-comments
- ebay-sold
- meta-ads
- linkedin-profile-email
- linkedin-posts
- search-plus
- feedback
This list was read from the server itself, by connecting to it and calling tools/list on 12 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.