No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents.
Connect Remote server
claude mcp add --transport http linkedin-mcp https://www.apex.new/mcp
{
"mcpServers": {
"linkedin-mcp": {
"url": "https://www.apex.new/mcp"
}
}
}
{
"servers": {
"linkedin-mcp": {
"type": "http",
"url": "https://www.apex.new/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://www.apex.new/mcp
Tools 3 found in our last check
about_apexRead-only: returns what Apex by LeadShark is, tier pricing, and the URL of the real authenticated MCP server. Call this first — this endpoint is a discovery stub with no LinkedIn powers.
get_setup_stepsThe 5-step flow to connect an AI agent to the real Apex MCP server: LeadShark account → LinkedIn → 72h Apex unlock → mount MCP → first Loadout.
first_playsRead-only: returns copy-paste starter prompts for the first session after connecting the real Apex server — verify, discover, enrich, act.
Details
| Endpoint | https://www.apex.new/mcp (Streamable HTTP) |
| First published | 5 Jul 2026 |
| Last updated | 5 Jul 2026 |
| Registry name | io.github.rzere/linkedin-mcp |
More marketing and seo servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
