Apex by LeadShark — discovery
Overview
Description from the maker (original English)
No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Marketing & social media
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://www.apex.new/mcpRun this in your terminal
claude mcp add --transport http linkedin https://www.apex.new/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"linkedin": {
"url": "https://www.apex.new/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"linkedin": {
"type": "http",
"url": "https://www.apex.new/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://www.apex.new/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account rzere, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Marketing & social mediai
- More stars than 0% of the other 3614 servers in this category
- Published to the registry more recently than 15% of the other 3614 servers in this category
- Basic checks equal to or better than 100% of the other 3614 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Apex by LeadShark — discovery safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Google Analytics MCP
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
BibiGPT YouTube Video Summarizer
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
linkedin-mcp
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.
The mission
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 loadout — 40 tools, See → Decide → Act
The full authenticated server at https://apex.leadshark.io/mcp equips your agent with:
See / discover — where is the demand? (Apex, except 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.
Decide / context — who is worth your time?
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.
Act — engagement
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.
Act — messaging
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).
Company Pages
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.
Pages & captured leads (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.
Automations & scheduled posts (Pro+ baseline)
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.
Safety, limits & history
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](https://www.apex.new/tools.md)
The safety model (this is the point)
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.
What this repo's server does
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.
Try it
Add https://www.apex.new/mcp as a custom connector / MCP server in your AI app, or run this repo locally:
node server.mjs # Node 18+, zero dependencies, listens on PORT (default 3000)Handshake by hand:
curl -s -X POST http://localhost:3000/mcp \-H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'
Get the full loadout
- Create a LeadShark account — free 7-day trial, no card.
- Connect the LinkedIn account the agent will operate.
- Unlock the one-time 24-hour Apex operator window (Settings → Apex Settings).
- Add
https://apex.leadshark.io/mcpto your AI app and authorize with LeadShark. - Ask: *"Check if you can see LeadShark Apex and list the tools available."*
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.
- Website: apex.new · Pricing: apex.new/pricing
- MCP setup guide: apex.leadshark.io/docs/mcp
- Agent operating guide: apex.new/agents.md
- Machine-readable index: apex.new/llms.txt
License
MIT