about_apex
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.
Takes no parameters.
Apex by LeadShark — discovery
io.github.rzerePublished by GitHub account rzerev1.0.0Updated Oct 24, 2026
No-auth discovery endpoint for Apex by LeadShark — governed LinkedIn hands for AI agents.
Overview
AI-generated overview
No-auth discovery stub for Apex by LeadShark that briefs an assistant on the paid LinkedIn automation loadout and how to connect it.
- What you can do
- Read what Apex by LeadShark is, its tier pricing and where the real authenticated server lives
- Get the five-step flow for connecting an AI agent to the full Apex server
- Retrieve copy-paste starter prompts for a first session: verify, discover, enrich, act
- When to use it
- Useful when you want an assistant to explain what the Apex LinkedIn loadout offers and walk you through signing up and mounting the real server. It has no LinkedIn capabilities itself, so it is only a briefing step before the paid product.
- Requirements
- Remote Streamable HTTP endpoint; no account, API key or headers needed. The README also notes it can be run locally with Node 18+ and no dependencies. Connecting the full Apex server requires a LeadShark account, a linked LinkedIn account and authorization.
Before you install
This endpoint only returns information; the actual LinkedIn actions live on a separate authenticated server. That full product is a paid subscription after a trial, and it operates a real LinkedIn account, so writes such as comments, connection requests and messages are budgeted, paced and sometimes queued for approval. The README mentions sending email through your own Resend account with your own key.
Installation
In SourceWeft
- Open Apex by LeadShark — discovery in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.rzere%2Flinkedin-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"apex-by-leadshark-discovery": {
"type": "http",
"url": "https://www.apex.new/mcp"
}
}
}README
linkedin-mcp
[Apex MCP — featured on mcpexplorer.com]
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
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:
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:
Handshake by hand:
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
Source: README.md at commit 3cff493
Tools
3get_setup_steps
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.
Takes no parameters.
first_plays
First Loadouts
Read-only: returns copy-paste starter prompts for the first session after connecting the real Apex server — verify, discover, enrich, act.
Takes no parameters.
Version history
1- v1.0.0LatestSep 16, 2026
Score
100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts