← engineeringleaders.io

INDIVIDUAL MCP TOOL

buy_reach

Answers 'how do we get in front of 3,300+ CEE engineering leaders, and what does it cost?' Builds a cart from ELC's nine published one-off reach items — newsletter section, dedicated newsletter, hosted meetup, podcast episode, decision-maker dinner, community survey, demo session, LinkedIn post, job listing — applies the published combo discount, and returns a decision-ready quote a human can sign.

engineeringleaders.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://www.engineeringleaders.io/mcp/trade

No auth detected

Connect to this endpoint to inspect the live schema for buy_reach and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description contains a write-action term.

Parent server

engineeringleaders.io

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.elc-trade]
url = "https://www.engineeringleaders.io/mcp/trade"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "elc-trade": {
      "type": "http",
      "url": "https://www.engineeringleaders.io/mcp/trade"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: elc-trade
Remote MCP URL: https://www.engineeringleaders.io/mcp/trade

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "elc-trade": {
      "url": "https://www.engineeringleaders.io/mcp/trade"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "elc-trade": {
      "type": "http",
      "url": "https://www.engineeringleaders.io/mcp/trade"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "elc-trade",
  "transport": "streamable-http",
  "url": "https://www.engineeringleaders.io/mcp/trade"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • get_more_tools — Check for additional specialised capabilities whenever your task might benefit from them.
  • get_started — START HERE for a greeting (hi, hello), a connectivity or liveness test, 'what can you do', or any question too general to match a specific tool.
  • benchmark_leadership_ratio — Answers 'what shape is my engineering org, and what should I ask about it?' Returns your manager-versus-senior-IC percentages and the resulting span (1 manager per N senior ICs), plus the question that shape usually raises.
  • assess_community_launch_readiness — Answers 'should I start an engineering-leadership meetup here?' A five-question readiness check taken from ELC's own new-city launch playbook — the one actually used to open Brno, Bratislava and Kraków — returning a verdict plus the specific gaps still open.
  • build_partnership_business_case — Answers 'how do I justify a community partnership budget internally?' Returns real reach numbers, the deliverables that serve the stated goal, where a proposed budget lands on the published ladder, and a forwardable approval email.
  • evaluate_meetup_topic — Answers 'will this topic fill a room?' Scores a proposed engineering-leadership meetup title and abstract against ELC's own topic-selection criteria — the ones behind 12 meetups a year at 120+ attendees since 2019 — and returns the specific failure modes, the title formulas that would fit, and the questions only the organiser can answer.
  • assess_speaker_readiness — Answers 'is this person ready to speak, and what will go wrong if they are not?' Checks a proposed speaker and talk against ELC's speaker vetting process — seven years of putting people in front of 120+ engineering leaders — and returns a readiness verdict with the specific gaps to close before the event.