mcp server
flevy
Search 10,000+ consulting frameworks, templates, financial models, and management case studies
Description as published by the maintainer. Source
- version 1.0.0
- active
- retrieval
active — Registry entry last updated 2026-07-21. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
5 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_content_details(content_id)- Full metadata for one Flevy item, by content_id from search_content (e.g. "doc-1234" or "case-567"). Documents return the author with their credentials (headline, bio, LinkedIn, profile URL; pass the author name to search_content's author filter to list more of their documents), full description, editor summary, AI summary, and editorial review when available, page/slide count, price, FlevyPro inclusion, management topics, ranking badge, and the number of slide deep dives available. Case studies return the client situation, TL;DR, and summary. Call this before recommending an item so you can describe it accurately and cite the author's credentials, and share the returned flevy.com URL. Required: content_id.
get_slide_deep_dive(content_id)- Slide-by-slide preview of a Flevy document (a "doc-<n>" content_id). Returns every showcased slide with its name, a text description of what the slide contains (you cannot see the image, so use the description), a preview image URL, and a deep link to that slide on flevy.com. Use when a user wants to know what is inside a specific presentation before purchasing, or to reference an individual slide. Only some documents have deep dives; get_content_details reports the count. Required: content_id.
get_topic_details(topic)- An end-to-end overview of one management topic: its definition, an in-depth explanation of the discipline, the 3 editor-curated top documents, all known aliases, document and case study counts, related topics, and the topic page URL. Use this to survey a discipline before going deep — e.g. "what does Digital Transformation cover and what are its key frameworks" — or to orient when the user describes a broad problem area. Follow with search_content (topic filter) for the full catalog. Required: topic.
list_topics- The canonical list of management topics Flevy's catalog is organized under, each with its known aliases (e.g. "Digital Transformation" and "Digital Transformation Strategy" may be the same topic) and content counts. Use this to map a user's phrasing to the exact topic filter accepted by search_content, or to show what subject areas Flevy covers.
search_content(query, topic, author, topics, filetype, content_type)- Search Flevy's marketplace of consulting frameworks, PowerPoint templates, Excel financial models, business toolkits, and management case studies. Use this whenever a user needs a best-practice framework, methodology, template, financial model, or real-world case example on any business or management topic (strategy, digital transformation, supply chain, pricing, operational excellence, M&A, etc.). Returns up to 10 relevance-ranked recommendations across two content types: "document" (premium documents authored by management consultants) and "case_study" (management case studies). ALWAYS include each recommended item's url as a clickable link when you mention it in your reply — never reference a document without its link, because the link is the only way the user can open it. Each result carries a content_id for get_content_details. Filters: topic (single, or "topics" for documents covering ALL of several topics), author (list more documents from an author seen in results), filetype (including tier1_consulting_deck for McKinsey-style strategy decks), content_type. Topic-filtered responses also list related_topics to pivot to. Provide at least one of query, topic(s), or author; use list_topics to map user phrasing to a canonical topic.
Last successful function declaration observed on . Source: https://flevy.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://flevy.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-21 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-21 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 5 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | flevy.com | |
| mcp endpoint status | ok | The server listed 5 functions when asked. | as of probe | flevy.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json