Apex by LeadShark — discovery
No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"linkedin-mcp": {
"url": "https://www.apex.new/mcp"
}
}
}Remote endpoints
https://www.apex.new/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢about_apex
Read-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.
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟢get_setup_steps
The 5-step flow to connect an AI agent to the real Apex MCP server: LeadShark account → LinkedIn → 72h Apex unlock → mount MCP → first Loadout.
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟢first_plays
Read-only: returns copy-paste starter prompts for the first session after connecting the real Apex server — verify, discover, enrich, act.
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}Community
Evidence