first_plays — Apex by LeadShark — discovery MCP Tool
first_plays
(first plays) is one of 3 tools on the
Apex by LeadShark — discovery
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call first_plays from your client
- Claude Code Apex by LeadShark — discovery first_plays run in your project directory
- Claude Desktop Apex by LeadShark — discovery first_plays ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Apex by LeadShark — discovery first_plays ~/.cursor/mcp.json
- VS Code Apex by LeadShark — discovery first_plays .vscode/mcp.json
- Zed Apex by LeadShark — discovery first_plays ~/.config/zed/settings.json
- Windsurf Apex by LeadShark — discovery first_plays ~/.codeium/windsurf/mcp_config.json
- Cline Apex by LeadShark — discovery first_plays ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Apex by LeadShark — discovery first_plays ~/.gemini/settings.json
- Grok Apex by LeadShark — discovery first_plays .mcp.json (in your project root)
- ChatGPT Apex by LeadShark — discovery first_plays Settings → Connectors → Advanced → Developer mode
- Claude.ai Apex by LeadShark — discovery first_plays Settings → Connectors → Add custom connector
- LangChain Apex by LeadShark — discovery first_plays pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http linkedin-mcp https://www.apex.new/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.