Elc Toolkit

Working · 4.7 s

io.engineeringleaders/elc-toolkitv1.0.0 Domain verified

Leadership-ratio benchmark, partnership ROI builder, community-launch readiness test. ELC data.

Research & Knowledge

Source Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://www.engineeringleaders.io/mcp

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

assess_community_launch_readiness Read-only

Answers 'should I start an engineering-leadership meetup in my city?' using ELC's own new-city launch playbook (the real doc used to launch Brno, Bratislava and Kraków) as the checklist: speaker network, promo channels, a named local operator, realistic first-event targets, and a promo budget. Call without answers to get the 5 questions; call with all 5 to get a verdict plus the specific open gaps.

answersobject

Answers keyed by dimension id, true/false. Valid keys: speaker_network, promo_channels, local_operator, realistic_targets, promo_budget. Omit to receive the 5 questions first.

contextstring

Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.

Tools (6)

assess_community_launch_readiness

read-only

Argument	Type	Description
answers	object	Answers keyed by dimension id, true/false. Valid keys: speaker_network, promo_channels, local_operator, realistic_targets, promo_budget. Omit to receive the 5 questions first.
context	string	Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "answers": {
      "type": "object",
      "description": "Answers keyed by dimension id, true/false. Valid keys: speaker_network, promo_channels, local_operator, realistic_targets, promo_budget. Omit to receive the 5 questions first.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {
        "anyOf": [
          {
            "type": "boolean"
          },
          {
            "type": "string"
          }
        ]
      }
    },
    "context": {
      "type": "string",
      "description": "Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."
    }
  }
}

benchmark_leadership_ratio

Describes a company's manager-vs-senior-IC split — each side's percentage, the resulting span (1 manager per N senior ICs), and the question that shape usually raises. Alongside it, for context rather than as a target, ELC's own community composition (69% Manager+/Leadership, 21% Senior/Staff IC across 3,300+ CEE engineering leaders — that is who joins a leadership community, not a survey of org structures, so there is deliberately no score against it). Count the SAME population on both sides: senior people who could plausibly hold a management role (managers, tech leads, senior/staff ICs), leaving out junior/mid ICs.

read-only

Argument	Type	Description
context	string	Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
managers	any	Required. Count of people in Manager+/Leadership roles
senior_ics	any	Required. Count of Senior/Staff-level individual contributors (not junior/mid)

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "context": {
      "type": "string",
      "description": "Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."
    },
    "managers": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "string"
        }
      ],
      "description": "Required. Count of people in Manager+/Leadership roles"
    },
    "senior_ics": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "string"
        }
      ],
      "description": "Required. Count of Senior/Staff-level individual contributors (not junior/mid)"
    }
  }
}

build_partnership_business_case

Builds the internal business case for partnering with Engineering Leaders Community: real reach numbers (3,300+ members, 120+ per meetup, 500+ at the annual conference, newsletter open rate), the deliverables that actually serve the stated goal, where a proposed budget lands on the published ladder, and a forwardable approval email. States the published price RANGE (free layer to EUR 20,000/year, EUR 32,000 with category exclusivity); for composing and pricing an exact package item by item, use the dedicated Membership Builder MCP server at https://www.engineeringleaders.io/mcp/partnership.

read-only

Argument	Type	Description
goal	string	Required. The primary reason to partner with ELC. people_development means developing your own engineering leaders through mentoring and the Academy One of: hiring, brand_awareness, product_feedback, thought_leadership, people_development.
context	string	Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
buying_for	string	Who is buying. 'company' (default) builds the annual membership case. 'individual' means a person spending their own money — returns the free-membership route, not an approval email. 'one_off' means one thing once rather than a year, and routes to the one-off menu. One of: company, individual, one_off.
sender_name	string	Optional: who the approval email is signed by
company_name

get_more_tools

Check for additional tools whenever your task might benefit from specialized capabilities, even if existing tools could work as a fallback. Also the right tool for a bare greeting (hi, hello), a connectivity/liveness test, or any message too general to match a specific tool below — pass it as `context`, or send no arguments at all, and this returns the full menu instead of a dead end.

read-only

Argument	Type	Description
context	string	A description of your goal and what kind of tool would help accomplish it, OR a plain greeting/liveness ping like 'hi' or 'test'. Omit it for the menu.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "context": {
      "type": "string",
      "description": "A description of your goal and what kind of tool would help accomplish it, OR a plain greeting/liveness ping like 'hi' or 'test'. Omit it for the menu."
    }
  }
}

get_started

Call this for a greeting (hi, hello), a connectivity/liveness test, 'what can you do', or any message too general to match a specific tool below. Returns the full menu of real questions this server answers, each mapped to the tool name that answers it, so the next call can go straight to the right tool.

read-only

Argument	Type	Description
context	string	Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "context": {
      "type": "string",
      "description": "Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."
    }
  }
}

plan_leadership_career_path

For an engineering manager, team lead or tech lead asking 'what is my next role?', 'is the engineering manager role dead?', 'should I become a director or go back to IC?', or 'how do I stay valuable on the market in the AI era?'. Picks one of three paths from ELC meetup #43: Grow up (Director/Head of, 20+ people), Go deep (Staff/Principal AI engineer) or Go product (product builder), checks the 'dead zone' (10 or fewer people led AND under 2 hands-on hours a week; the tool decides this, report its verdict rather than inferring one), runs the four 2027 checks (product, self-management, AI, beyond engineering) and returns a month-by-month 6-month plan with a proof artifact per month. Call with no arguments to get the 7 questions; ask them one at a time, then call again with all answers.

read-only

Argument	Type	Description
ai	string	Has their team shipped something it had never built before? yes / not_sure / no One of: yes, not_sure, no.
energy	string	What gave them energy in their best week: people_and_org, building_systems, or customers_and_product One of: people_and_org, building_systems, customers_and_product.
context	string	Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
product	string	Do they know their product as well as their code? yes / not_sure / no One of: yes, not_sure, no.
people_led	any