No-auth discovery endpoint for Apex by LeadShark β governed LinkedIn hands for AI agents.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Governed LinkedIn hands for AI agents. This is the public face of Apex by LeadShark β an MCP loadout that lets Claude, ChatGPT, or Cursor operate a real LinkedIn account in plain English: find buyers, rank intent, comment, connect, and message. Every action is paced, capped, approval-queued where needed, and fully logged.
This repo contains the discovery endpoint β a minimal, dependency-free MCP server, served live at:
https://www.apex.new/mcp (alias: https://www.apex.new/linkedin-mcp)Mount it in any MCP host and it completes the handshake instantly β no account, no auth β then briefs your agent on what the full loadout is and how to get it.
Most LinkedIn tooling automates what you already decided: schedule this post, DM whoever comments. Apex is the layer above that β the intelligence that decides what to automate and where to show up. The activation path is intelligence-first, not automation-first. In five words:
Discover demand. Engage with context.
An agent running Apex works a loop: See β Decide β Act. Find the posts and people where attention already is, figure out who's worth engaging and with what angle, then engage β inside the account's safety budget.
The full authenticated server at https://apex.leadshark.io/mcp equips your agent with:
discover_lead_magnets)search Β· discover_lead_magnets Β· list_signals Β· feed Β· list_recent_posts Β· list_person_posts Β· list_post_engagers Β· get_person_activity
Find people and companies, pull a continuously refreshed radar of prospect-rich lead-magnet posts, list your heat-scored inbound signals, turn one viral post into a warm lead list, and see the rooms a prospect is already in (get_person_activity β who they comment on, what they react to). discover_lead_magnets is available on the Pro+ MCP floor (it doubles as content market-signal); the rest of this group is Apex.
enrich Β· enrich_company Β· get_lead_activity
Structured profiles for a person or account: role, company, activity, connections. The agent ranks ICP fit and intent and picks the angle β comment, connect, or ignore. Built on enrich, the most-used signal in the loadout.
comment_on_post Β· react_to_post Β· send_connection_request Β· engage_with_comment Β· manage_invitations
Show up where the prospect's attention already is β warm them up in public before anything lands in their inbox. Triage inbound connection requests too.
list_recent_messages Β· get_messages_with_person Β· send_message Β· send_email
Read the inbox, pull a full thread with one person, send the DM β deduped, paced, and logged. send_email sends through your own connected Resend account (BYO key).
list_companies (Pro+) Β· comment_as_company Β· react_as_company Β· manage_company_reply_automations
List and schedule to pages you administer on Pro+; acting in the page's voice β commenting, reacting, and running reply-only comment automations as the page β is Apex.
list_lead_pages Β· get_page_leads Β· list_lead_magnet_links
Read the leads your lead magnets captured β pages with capture stats, the deduped enriched email leads for a page, and your standalone leads.sh capture links β to feed the enrich β act loop.
create_automation Β· list_automations Β· get_automation Β· edit_automation Β· suggest_automation_settings Β· schedule_post_with_automation Β· list_scheduled_posts Β· get_scheduled_post Β· edit_scheduled_post Β· cancel_scheduled_post
The execution layer: commentβDM lead-magnet automations and pre-automated post scheduling. Apex decides what to run; these run it.
manage_activity_limits Β· set_daily_dm_limit Β· list_actions
Check budgets before acting, adjust caps, and read the audit trail β what the agent already did, what's staged for approval, why something was refused, and the current safety mode.
Full per-tool reference (parameters, access, tiers): apex.new/tools.md
Every write the agent makes shares the same daily/weekly budgets as the account's automations (DMs, replies, connections), honors the do-not-engage list, and is paced and rate-limit-aware. Actions can be refused or queued for the user's approval β and the agent is told why. Limits are calibrated from LeadShark's production LinkedIn volume, not guesswork. Agents are expected to check list_actions before acting and to work within limits rather than around them.
This discovery stub speaks MCP over Streamable HTTP (JSON-RPC 2.0 over POST, JSON responses, stateless, no SSE) and exposes three no-auth informational tools:
| Tool | What it returns |
|---|---|
about_apex | What Apex is, tier pricing, trial paths, key links |
get_setup_steps | The 5-step connect flow (account β LinkedIn β 24h unlock β mount MCP β first play) |
first_plays | Copy-paste starter prompts: verify, discover, enrich, act |
It has no LinkedIn powers of its own β it's the handshake and the briefing, not the hands.
Add https://www.apex.new/mcp as a custom connector / MCP server in your AI app, or run this repo locally:
Handshake by hand:
https://apex.leadshark.io/mcp to your AI app and authorize with LeadShark.Apex is $119/mo after the trial. LeadShark Pro ($39/mo) automates your lead magnet; Pro+ ($59/mo) scales automations and gated funnels; Apex is the operator loadout on top.
MIT
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/apex-by-leadshark-discovery)<a href="https://allmcps.com/mcp/apex-by-leadshark-discovery"><img src="https://allmcps.com/api/badge/apex-by-leadshark-discovery?style=directory" alt="Apex by LeadShark β discovery on AllMCPs" /></a>