# Two Minute Toolkit (remote · www.twominutetoolkit.com) 20 slide-ready chart tools: Gantt, SWOT, 2×2, RACI, org chart, mind map, fishbone. Free. - Trust score: 76/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `www.twominutetoolkit.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-twominutetoolkit-toolkit/www.md), [page](https://verifymcp.io/servers/com-twominutetoolkit-toolkit/www) ## Channel facts - Endpoint: `https://www.twominutetoolkit.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.0.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Endpoint Security**: 80/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 74/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 14617 tokens (~730/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. - Tools include usage examples. - **Stability & Change Management**: 17/100 - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the Two Minute Toolkit MCP server? Two Minute Toolkit is a hosted endpoint at https://www.twominutetoolkit.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http com-twominutetoolkit-toolkit 'https://www.twominutetoolkit.com/mcp' ``` ### Cursor ```json { "mcpServers": { "com-twominutetoolkit-toolkit": { "url": "https://www.twominutetoolkit.com/mcp" } } } ``` ### VS Code ```json { "servers": { "com-twominutetoolkit-toolkit": { "type": "http", "url": "https://www.twominutetoolkit.com/mcp" } } } ``` ### Codex ```toml [mcp_servers.com-twominutetoolkit-toolkit] url = "https://www.twominutetoolkit.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-twominutetoolkit-toolkit": { "type": "remote", "url": "https://www.twominutetoolkit.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-twominutetoolkit-toolkit --url 'https://www.twominutetoolkit.com/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-twominutetoolkit-toolkit: url: "https://www.twominutetoolkit.com/mcp" ``` ### Netclaw ```json { "McpServers": { "com-twominutetoolkit-toolkit": { "Transport": "http", "Url": "https://www.twominutetoolkit.com/mcp" } } } ``` ### Vellum ```bash assistant mcp add com-twominutetoolkit-toolkit -t streamable-http -u 'https://www.twominutetoolkit.com/mcp' ``` ### Other ```json { "mcpServers": { "com-twominutetoolkit-toolkit": { "type": "http", "url": "https://www.twominutetoolkit.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 76, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-03 (score 75, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-01 (score 74, +1) - [functional improvement] Stability: unverified → 0.03 ### 2026-10-31 (score 73) First indexed and scored. ## MCP tools (20) ### `create_timeline` (~508 tokens) Two Minute Timeline Generate a slide-deck-quality Gantt timeline: task bars and milestone diamonds laid out across numbered time columns (weeks, sprints, months), with optional labelled section bands that group tasks into phases. Choose it for project plans, roadmaps, launch schedules and anything where WHEN each piece of work happens is the point; use a process diagram instead when only the order of phases matters. Limits: 2–52 columns, up to 100 rows. Set duration 0.25 for a milestone. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `columns` (integer): Number of time columns across the chart (2–52, default 8). - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `labelsInBars` (boolean): Draw each task's name inside its bar (and beside milestone diamonds). Default true. - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `start` (integer): Number of the first column, so 1 gives "Week 1, Week 2…" (default 1). - `tasks` (array, required): Rows in the chart, top to bottom (up to 100). Normally just task bars and milestones, which is all most timelines need. Section bands ({ "type": "section" }) may optionally be inserted to group the t… - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `unit` (string): Column unit label, e.g. "Week", "Sprint", "Month", "Day", "Q". Headers read " ". Default "Week". - `width` (integer): Chart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the content. ### `create_harvey_matrix` (~649 tokens) Two Minute Harvey Ball Matrix Generate a slide-deck-quality Harvey ball matrix: options as rows scored against criteria as columns, every cell drawn in one style (Harvey balls 0–4 from empty to full, ticks 0/1, or 0–5 dots), with an optional highlighted 'Recommended' row, an optional notes column (appears when any row has notes) and a legend. Choose it to compare vendors, tools, plans or features side by side; use a timeline when the point is WHEN work happens, a process for ordered steps, a pyramid/funnel for a hierarchy or narrowing stages, and a hub and spoke, mind map or org chart for relationships. Limits: 2–12 rows, 1–8 criteria, row names up to 40 characters; scores outside the style's range are clamped and null leaves a cell blank. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `criteria` (array, required): Column headings, left to right: what each option is scored on, e.g. ["Cost", "Ease of use", "Integrations"]. 1–8 criteria, up to 40 characters each; long names wrap to two lines. - `legend` (boolean): Show a one-line legend under the grid explaining the scale. Default true. - `notes` (boolean): Show the Notes column on the right. true shows it even when no row has a note yet; false hides it (any row notes are kept but not drawn). When omitted, the column appears automatically as soon as any… - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `rows` (array, required): The options being compared, top to bottom (2–12). Each has a name and one score per criterion, in the same order as `criteria`. - `style` (string): Cell style for the whole grid: "harvey" (Harvey balls, scores 0–4 from empty to full), "check" (a tick for 1, nothing for 0) or "dots" (0–5 filled dots out of five). Default "harvey". - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the content. ### `create_process` (~566 tokens) Two Minute Chevron Process Generate a slide-deck-quality chevron process diagram: 2–7 phases drawn as arrow-shaped chevrons left to right, each with an optional timing line ("Weeks 1–2") and up to 5 short bullets beneath it, and an optional "you are here" highlight on one phase. Choose it for an "our approach" or methodology slide, delivery phases, a sales or onboarding process, or any short linear sequence where the ORDER of the phases matters; use a timeline instead when exact dates and overlapping durations matter, a cycle diagram when the last step loops back to the first, and an org chart or mind map for branching structures. Limits: 2–7 steps, up to 5 bullets per step; keep step names to one to three words and bullets to a short phrase. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `current` (integer): Optional highlight: the 0-based index of one step (0 is the first step). A pointer with a label (currentLabel, default "You are here") appears above that step; every step keeps its colour. Omit for n… - `currentLabel` (string): Text above the pointer on the highlighted step (only shown when current is set). Default "You are here"; e.g. "We are here", "Today", "Current phase". - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `steps` (array, required): The phases, left to right (2–7; extra steps are dropped with a warning). Each step is one chevron with its name inside, an optional timing line just under it and optional bullets beneath. Keep names… - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the content. ### `create_org_chart` (~548 tokens) Two Minute Org Chart Generate a slide-deck-quality org chart: a tree of people cards (name, role, initials circle) joined by elbow connectors, top-down or left-right. Colour is automatic: each team under the root (each of the root's direct reports and everyone below them) gets its own palette colour; set `color` on a card only to override that. Choose it whenever the point is WHO reports to or works with whom: reporting lines, project or engagement teams, governance and steering structures. Use a mind map instead for ideas or topics radiating from a central theme, and a hub and spoke for one centre with peers around it. Nest people in `children` under `root`; more than 4 reports with no reports of their own are stacked in a column automatically. Limits: 60 people, 5 levels. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `layout` (string): "top-down" (default): the root at the top, reports in rows below. "left-right": the root on the left, reports in columns to the right, which suits deep or very wide trees. - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `root` (required): The top of the tree (the lead, manager or sponsor) with everyone else nested under it in `children`. Limits: 60 people and 5 levels in total (the root is level 1); extra people are dropped with a war… - `showInitials` (boolean): Show an initials circle on each card, in the card's team colour. Default true. There are no photos. - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x. ### `create_mind_map` (~571 tokens) Two Minute Mind Map Generate a slide-deck-quality mind map: a central topic pill with up to 8 colour-coded branches of sub-topics radiating left and right (or all to the right, like an outline), joined by smooth tapered curves. Choose it for brainstorms, idea or theme breakdowns, workshop outputs, feature or research groupings and anything that unpacks ONE central idea into related topics with no order or reporting line; use an org chart instead for people and who reports to whom, a hub and spoke for one centre with a single ring of peers, and a process or cycle when the order matters. Nest sub-topics in `children` under each branch. Limits: 8 branches, 3 levels below the centre, 50 topics; keep labels to a few words. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `branches` (array, required): Required: the first-level branches around the centre (up to 8; an empty list draws just the centre), each with optional nested `children` (up to 3 levels below the centre and 50 topics in total; extr… - `center` (string, required): The central topic, drawn as a bold pill in the middle, e.g. "Customer retention". Required. Keep it short; long text wraps onto two lines. - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `layout` (string): "balanced" (default): branches split between the left and right of the centre so both sides are about the same height, the classic mind-map look. "right": every branch to the right of the centre, lik… - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x. ### `create_cycle` (~558 tokens) Two Minute Cycle Diagram Generate a slide-deck-quality cycle diagram: 3–8 stages evenly spaced around a loop, first stage at 12 o'clock running clockwise, joined by arrows that lead from the last stage back to the first, with an optional centre label and a short detail line beside each stage. Two looks: "nodes" (coloured circles on a ring with curved arrows) and "segments" (a ring cut into arrow-shaped segments). Choose it when the process repeats: improvement loops (plan-do-check-act), flywheels, product or customer lifecycles, feedback loops. Use a process diagram instead when steps run once from start to finish, a timeline when dates matter, and hub and spoke when the items surround a centre with no order. Limits: 3–8 stages, names of 1–3 words, details of about 12 words. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `center` (string): Optional label in the middle of the loop, e.g. the goal the cycle serves ("Customer value"). Bold, wrapped to up to 3 lines. Omit for none. - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `stages` (array, required): The stages in order (3–8). The first sits at 12 o'clock and the loop runs clockwise, back from the last stage to the first. Fewer than 3 still render but are reported as a warning; more than 8 are dr… - `style` (string): "nodes" (default): coloured circles on a ring joined by curved arrows, stage names inside the circles. "segments": a thick ring cut into coloured arrow-shaped segments, stage names outside. - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x. ### `create_hub_spoke` (~592 tokens) Two Minute Hub and Spoke Generate a slide-deck-quality hub and spoke diagram: a large central hub circle with 3–10 coloured satellite cards evenly spaced around it, each joined to the hub by a spoke, with an optional short detail beside each satellite and optional arrowheads (out from the hub, or both ways). Choose it when several items relate to one centre with no order between them: a platform and its products or integrations, a team and its stakeholders, a core value and its pillars, a company and its partners. Use a cycle when the items form a repeating sequence, a process diagram for one-way steps, a mind map when the satellites branch further, and an org chart for reporting lines. Limits: 3–10 spokes, one level only, names of 1–3 words, details of about 12 words. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `arrows` (string): Arrowheads on the spokes: "none" (default, plain connecting lines), "out" (from the hub towards each satellite, e.g. distribution or influence), "both" (two-way exchange). - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `hub` (string, required): Label of the central hub, e.g. "Core platform". Bold white text in a large circle, wrapped to up to 3 lines; 1–4 words reads best. - `hubColor` (string): Optional hex colour of the hub circle. Default: the first palette colour (indigo #4f46e5), with the spokes taking the following palette colours. - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `spokes` (array, required): The satellites around the hub (3–10), placed clockwise from 12 o'clock. Order only decides placement; nothing implies a sequence. Fewer than 3 still render but are reported as a warning; more than 10… - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x. ### `create_pyramid` (~507 tokens) Two Minute Pyramid / Funnel Generate a slide-deck-quality pyramid or funnel: 2–8 stacked layers in even steps, narrow at the top in pyramid mode (a hierarchy of needs, a strategy pyramid, foundations to vision) or wide at the top in funnel mode (sales, marketing or hiring funnels). Each layer has a name and an optional detail line beside it. Choose it when items stack in a ranked order or narrow down stage by stage; use a process diagram for a sequence of phases of equal weight, a cycle for a loop, a hub and spoke for parts around a centre, and a timeline when dates matter. Limits: 2–8 layers; keep names to one to four words and details to one short sentence. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `layers` (array, required): The layers, top to bottom (2–8; extra layers are dropped with a warning). In a pyramid the first layer is the narrow tip; in a funnel it is the wide first stage. Names sit inside the shape when they… - `mode` (string): "pyramid" (default) narrows toward the top layer, for hierarchies and foundations-to-vision stacks. "funnel" is widest at the top and narrows down, for sales, marketing and hiring stages. Layers are… - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x. ### `create_football_field` (~948 tokens) Two Minute Football Field Chart Generate a slide-deck-quality football field chart, the valuation summary used in banking and corporate-development decks: one floating horizontal bar per method from its low to its high value on a shared axis with round gridlines, the method name and an optional assumption line ("8.0x–10.0x EV/EBITDA") on the left, low and high values printed at the bar ends, up to 3 dashed marker lines (current share price, offer price) and an optional shaded implied range. Choose it for valuation ranges (DCF, trading comps, precedent transactions, 52-week range, analyst targets, LBO) and for any comparison of low–high ranges on one scale, such as salary bands, cost or estimate ranges, or price ranges by scenario. Use a timeline (Gantt) when the ranges are dates, a Harvey ball matrix for scores against criteria, and a pyramid/funnel for stage volumes. Values are plain numbers; set prefix ("$", default), suffix ("m", "/sh", "x") and decimals for display. Limits: 1–12 rows, 0–3 markers; a low above its high is swapped with a warning. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `axisMax` (number): Optional right end of the value axis, e.g. 70. Omit (recommended) and the axis ends at a round number slightly above the largest value. - `axisMin` (number): Optional left end of the value axis, e.g. 30. Omit (recommended) and the axis starts at a round number slightly below the smallest value. Bars beyond the axis are cut off with a warning. - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `decimals` (integer): Decimal places for every value (0–3), e.g. 2 shows 45.10. Omit (the default) to show each value as given, rounded to at most 2 decimals. - `markers` (array): Optional vertical dashed reference lines across every row (0–3), each labelled at the top with its label and value, e.g. [{ "label": "Current price", "value": 45.1 }, { "label": "Offer", "value": 52… - `palette` (array): Hex colours. Every bar takes the FIRST palette colour unless the row sets its own colour, so a brand colour as the first entry recolours the whole chart. Default: indigo, sky, emerald, amber, red, gr… - `prefix` (string): Text put before every value, default "$". Use "€", "£" or "" (none), e.g. "" for multiples. - `range` (object): Optional shaded band behind every row, e.g. the implied valuation range: { "low": 48, "high": 55, "label": "Implied range" }. Its label and values are shown above the band. Omit for none (the default… - `rows` (array, required): The valuation methods, top to bottom (1–12; extra rows are dropped with a warning). Each row is one horizontal bar from low to high on the shared axis, e.g. { "method": "Trading comps", "detail": "8.… - `showValues` (boolean): Print the low and high values just outside each end of every bar. Default true. - `suffix` (string): Text put after every value, default "" (none). E.g. "m" for $ millions, "/sh" for per share, "x" for multiples, "%" for percentages. - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the number of rows. ### `create_five_forces` (~817 tokens) Two Minute Porter's Five Forces Generate a slide-deck-quality Porter's five forces diagram laid out as the classic cross: competitive rivalry in the centre, threat of new entrants above, threat of substitutes below, bargaining power of suppliers on the left and of buyers on the right, with arrows pointing in at the centre. Each box has a header band with the force's name, an optional rating pill (very low, low, medium, high, very high; green, amber or red) and up to 5 short bullets of evidence; an optional conclusion line sits underneath. Choose it to assess an industry's attractiveness or competitive pressure for a strategy, market-entry, investment or case-interview slide. Use a Harvey ball matrix to score several options against criteria, a hub and spoke for items around a centre with no fixed meaning, and a mind map for open-ended brainstorming. All five forces are required (an empty object {} is fine); infer sensible ratings and bullets from the industry rather than asking. Limits: 5 bullets per force of about 4–10 words, a conclusion of one sentence. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `buyers` (object, required): Right box: how much leverage customers have to push prices down or demand more. Default name "Bargaining power of buyers". E.g. { "rating": "high", "bullets": ["Riders compare fares in seconds"] }. - `conclusion` (string): Optional one-line takeaway shown in a muted band under the cross, e.g. "Overall: moderately attractive; buyer power is the main threat". Wraps to 2 lines. Omit for none. - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `newEntrants` (object, required): Top box: how easily new competitors can enter the industry (capital needs, scale, brand, regulation). Default name "Threat of new entrants". E.g. { "rating": "high", "bullets": ["Network effects favo… - `palette` (array): Hex colours. Every header band takes the FIRST palette colour unless a force sets its own colour; rating pills always use green, amber and red. Default: indigo, sky, emerald, amber, red, gray. - `rivalry` (object, required): Centre box: how intensely existing competitors fight on price, product, marketing and service. Default name "Competitive rivalry". E.g. { "rating": "high", "bullets": ["Price war among the top two pl… - `showRatings` (boolean): Show each force's rating pill. Default true; false hides every rating without deleting it. - `substitutes` (object, required): Bottom box: how easily customers can meet the same need another way. Default name "Threat of substitutes". E.g. { "rating": "high", "bullets": ["Public transit and micromobility"] }. - `suppliers` (object, required): Left box: how much leverage suppliers (inputs, labour, platforms) have over prices and terms. Default name "Bargaining power of suppliers". E.g. { "rating": "high", "bullets": ["Drivers multi-home ac… - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x. ### `create_sipoc` (~896 tokens) Two Minute SIPOC Diagram Generate a slide-deck-quality SIPOC diagram: five equal columns headed by big coloured letters, Suppliers, Inputs, Process, Outputs and Customers, with chevrons between them for the flow. Suppliers, inputs, outputs and customers are stacked cards; the process is 2–7 numbered step boxes joined by down arrows, with an optional process name and optional "Starts when" and "Ends when" boundaries. Choose it for Lean and Six Sigma project scoping (the Define phase of DMAIC), process-improvement kick-offs, quality and ISO documentation, and any slide that frames a process by who feeds it and who it serves; use a chevron process instead for a simple left-to-right sequence of phases with no inputs or outputs, an issue tree to break a problem into causes, and a timeline when dates matter. Limits: 1–7 steps (2 or more expected), up to 8 items in each of the other four columns; keep each item to a short phrase and start steps with a verb. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `colors` (object): Optional colour overrides per column, keyed by its letter, e.g. {"p": "#0f766e"}. Columns without one take the palette colours in order: S the first, I the second, P the third, O the fourth, C the fi… - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `customers` (array): Who receives the outputs (0–8), one card each, e.g. ["Customer", "Finance"]. Internal teams count as customers too. - `end` (string): Optional end boundary: the event that completes the process, shown below the steps as "Ends when …", e.g. "Payment is received". Omit for none. - `inputs` (array): What the suppliers provide to the process (0–8), one card each, e.g. ["Purchase order", "Stock levels"]. - `numbered` (boolean): Number the process steps 1, 2, 3… in coloured circles. Default true; false shows plain step boxes. - `outputs` (array): What the process produces (0–8), one card each, e.g. ["Shipped order", "Invoice"]. - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `process` (string): Optional name of the process, shown in bold at the top of the Process column, e.g. "Order to cash". Omit for none. Wraps to two lines, then truncates. - `start` (string): Optional start boundary: the trigger that begins the process, shown above the steps as "Starts when …", e.g. "Customer places an order". Omit for none. - `steps` (array, required): Required: the high-level process steps, top to bottom (1–7, ideally 4–7; fewer than 2 renders with a warning, extras are dropped with a warning). Each is a step box joined to the next by a down arrow… - `suppliers` (array): Who provides the inputs (0–8; extras are dropped with a warning), one card each, e.g. ["Customer", "Sales team", "Warehouse"]. Short phrases; long ones wrap onto up to four lines. - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the tallest column. ### `create_issue_tree` (~663 tokens) Two Minute Issue Tree Generate a slide-deck-quality issue tree or driver tree: a key question, problem or top-line metric on the left, broken down left to right into drivers, sub-drivers and hypotheses in clean columns of rounded boxes joined by elbow connectors. Each first-level branch takes its own palette colour. Any box can carry a `value` ("$12.4m", "+3% YoY") and any parent an `operator` ("+", "-", "x", "/", drawn as + − × ÷ where its children join) for KPI and value driver trees (Profit = Revenue − Costs; Revenue = Customers × Revenue per customer); `levels` labels the columns and `numbered` adds 1, 1.1, 1.1.1. Choose it for consulting issue trees and MECE breakdowns, hypothesis trees, KPI, value and driver trees, root-cause and problem trees: anything where a parent is logically made up of its children. Use a mind map instead for loose brainstorms radiating from a centre with no hierarchy logic or values, and an org chart for people and reporting lines. Limits: 4 levels including the root, up to 6 children per box, 40 boxes; keep labels to a few words. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `levels` (array): Optional column labels, left to right, printed in small caps above each level, e.g. ["Key question", "Drivers", "Sub-drivers", "Hypotheses"] (0–4). Omit for none. - `numbered` (boolean): Prefix every box below the root with its outline number, 1, 1.1, 1.1.1, as consultants number issue trees. Default false. - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `root` (required): The key question, problem or top-line metric on the left (e.g. "Why has profitability declined?" or "Operating profit"), with its drivers nested in `children`. Limits: 4 levels in total including the… - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x. ### `create_ecomap` (~660 tokens) Two Minute Ecomap Generate a clean ecomap (ecological map, Hartman style) for social work, family therapy, case management and school counselling: the client or household in a solid centre circle with its members listed inside, and 2–12 system circles around it (school, work, extended family, church, health care, probation, friends…), each joined to the centre by a line whose style shows the relationship: strong (thick line), moderate (plain line, the default), tenuous (dashed) or stressful (hatched red line). Arrowheads show the flow of energy or resources: to the system, from it, or both ways. Each system may carry a short detail outside its circle, and a legend of the line styles sits underneath. Choose it to map a person's or family's relationships with outside systems; use a hub and spoke for neutral parts around a centre with no relationship quality, a mind map when the items branch further, and an org chart for reporting lines. Limits: 2–12 systems, 0–8 household members, system names of 1–3 words, details of about 10 words. Use first names or roles only; never put identifying client details in the chart. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `center` (object, required): The client or household in the middle: a solid circle in the first palette colour with the name in bold white and the members listed under it, e.g. { "name": "Lopez household", "members": ["Maria, 34… - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `legend` (boolean): Show the legend under the map explaining the four line styles and the arrows. Default true; set false when the audience already knows the notation. - `palette` (array): Hex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray. - `systems` (array, required): The systems around the centre (2–12), placed clockwise from 12 o'clock: people, groups and services such as School, Work, Extended family, Church, Health care, Friends, Probation, Benefits. One syste… - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x. ### `create_lab_fishbone` (~724 tokens) Two Minute Lab Fishbone Generate clean lab fishbone diagrams (lab value skeletons), the shorthand nurses, residents and students use in notes and case presentations: BMP / Chem-7 (Na | Cl | BUN over K | HCO3 | Cr with glucose in the tail), CBC (WBC > Hgb over Hct < Plt), coags (PT | PTT over INR), LFT (TP | AST | T bili over Alb | ALT | ALP), ABG (pH / pCO2 / pO2 / HCO3) and Ca/Mg/Phos, each with an optional caption such as a time, in a tidy grid. Numeric values outside adult reference ranges are flagged red with ↑ or blue with ↓ (US or SI ranges; overridable per value), and the result also includes a plain-text version to paste into a note. Choose it whenever lab results should be shown in fishbone form; it is not a cause-and-effect (Ishikawa) diagram, for which use create_fishbone. Values are strings of up to 8 characters; 1–8 panels. A drawing aid only, not clinical decision support: never include patient names or identifiers, because links carry the data. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `flag` (boolean): Flag numeric values outside the adult reference range: red with ↑ when high, blue with ↓ when low. Default true. Manual `flags` on a panel apply either way. Ranges vary by lab; this is a drawing aid,… - `labels` (boolean): Show a small analyte name (Na, K, Hgb…) beside every value. Default false: experienced readers know the positions; turn it on for teaching or for readers new to the shorthand. - `palette` (array): Hex colours; only the first is used, for the small panel-type tags. The skeletons stay monochrome, and flags are always red (high) and blue (low). - `panels` (array, required): The panels to draw (1–8), in order, two or three per row. Each has a `type` and its values as flat string keys; leave a key out to leave its position blank. More than 8 are dropped. - `title` (string): Heading shown top-left at 22px bold, e.g. "Day 3 labs". An empty string hides it. Never put a patient name or identifier here: links carry the chart itself. - `units` (string): Which reference ranges the automatic flags use: "US" (conventional units: mg/dL, g/dL, %, mmHg; the default) or "SI" (mmol/L, µmol/L, g/L, L/L, kPa). It does not convert values. - `width` (integer): Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x. ### `create_quadrant_matrix` (~1280 tokens) Two Minute 2×2 Matrix Generate a slide-deck-quality 2×2 matrix, the classic consulting quadrant slide: two labelled axes (name plus low and high ends, rotated on the left) and four quadrants tinted in one accent colour. Two modes: "plot" places items as dots at x and y on 0–10 scales (or bubbles sized by `size`), with every label placed automatically so none overlap and quadrant names faint in the corners; "list" gives each quadrant a bold name and up to 6 bullets. Choose it to prioritise or position things on two dimensions: tasks, initiatives, features, products, brands, stakeholders or risks. Pick the preset that matches the request and let it supply the standard axes, quadrant names and mode: impactEffort for impact vs effort, quick wins or an action priority matrix; eisenhower for urgent vs important or a to-do list; bcg for a growth-share or product portfolio matrix (give revenue as size); ansoff for growth strategy (products × markets); powerInterest for a stakeholder map; perceptual for a perceptual or competitive positioning map (rename the axes to the user's attributes); riskLikelihood for a likelihood vs impact risk grid; none for any other 2×2 (name the axes and quadrants yourself; an omitted preset means none). Quadrants are keyed by position: topLeft, topRight, bottomLeft, bottomRight; with normal axes topRight is high x, high y. Use a Harvey ball matrix to score options against several criteria, create_five_forces for one industry's competitive forces, and create_swot for strengths, weaknesses, opportunities and threats. Infer realistic positions from context rather than asking. Limits: 30 items, names up to 40 characters (1–4 words read best), 6 bullets per quadrant. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `items` (array): Plot mode only (kept but not drawn in list mode): 0–30 items, each a dot at its x and y on 0–10 scales, with its name beside it, e.g. { "name": "Self-serve onboarding", "x": 2.5, "y": 8 }. Labels are… - `mode` (string): "list": four tinted quadrants, each with its name and bullets. "plot": items drawn as dots or bubbles at their x and y, with quadrant names faint in the corners. Omit to use the preset's mode (list f… - `palette` (array): Hex colours. The whole matrix uses the FIRST palette colour as its one accent, tinted in four strengths across the quadrants, so a brand colour as the first entry recolours the chart. Default: indigo… - `preset` (string): Set it: the standard matrix to start from, or "none" (the default when omitted). Its axis labels, quadrant names and mode fill in anything the payload leaves out (your own values always win). eisenho… - `quadrants` (object): The four quadrants by POSITION on the slide (after any axis reversal): topLeft, topRight, bottomLeft, bottomRight. With both axes in their normal direction, topRight is high x and high y, bottomLeft… - `showGrid` (boolean): Plot mode: light gridlines at every whole unit (1–9) behind the items. Default false (the midlines only). - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height follows from the width (plot mode) or the bullets (list mode). - `xAxis` (object): The horizontal axis along the bottom, e.g. { "label": "Effort", "low": "Low", "high": "High" }. Each field you omit comes from the preset; an empty string hides that text. - `yAxis` (object): The vertical axis up the left side, with rotated texts, e.g. { "label": "Impact", "low": "Low", "high": "High" }. Each field you omit comes from the preset; an empty string hides that text. ### `create_fishbone` (~792 tokens) Two Minute Fishbone Diagram Generate a slide-deck-quality fishbone diagram (Ishikawa or cause-and-effect diagram) for root-cause analysis: a horizontal spine ending in a head box that holds the problem, with 1–8 category bones angled off it, alternating above and below, each named in a coloured pill and carrying up to 6 causes, and each cause up to 3 sub-causes. Standard category sets fill in unnamed categories: 6M for manufacturing (People, Machine, Method, Material, Measurement, Environment), 8P for services and 4S for the service industry. Choose it for quality, Lean and Six Sigma (DMAIC Analyze) work, healthcare quality improvement, incident reviews and any "why does this keep happening" slide; use an issue tree for a MECE logic or KPI breakdown, a mind map for an open brainstorm, a SIPOC to scope a process, and the lab fishbone (create_lab_fishbone) for lab value skeletons such as BMP or CBC, which is a different thing. Infer 4–6 categories and 2–4 causes each from the problem rather than asking. Limits: 1–8 categories, 6 causes per category of about 2–7 words, 3 sub-causes per cause. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `categories` (array, required): The category bones (1–8; 4–6 is typical), drawn left to right in pairs: the first above the spine, the second below it, the third above, and so on. More than 8 are dropped with a warning. E.g. [{ "na… - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `palette` (array): Hex colours applied in order to the category bones that have no colour of their own (bone, cause lines and name pill). Pass the user's brand colours here when they name them. Default: indigo, sky, em… - `preset` (string): Standard category set whose names are used for categories that have no `name`, by position: "6m" (manufacturing: People, Machine, Method, Material, Measurement, Environment), "8p" (services: Product,… - `problem` (string, required): The effect being analysed, shown in the head box at the right end of the spine, e.g. "Late medication administration on Ward 4B". Phrase it as a problem, not a cause. Wraps to 5 lines in the box; abo… - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the content: bones grow as long as their causes need. ### `create_swot` (~868 tokens) Two Minute SWOT Analysis Generate a slide-deck-quality SWOT analysis laid out as the classic 2×2 grid: Strengths (top left) and Weaknesses (top right) as the internal row, Opportunities (bottom left) and Threats (bottom right) as the external row, each a softly tinted panel with its big coloured letter and up to 8 bullets, with optional Helpful / Harmful and Internal / External axis labels, an optional subject ("Acme Coffee, FY26") and an optional one-line conclusion underneath. Choose it to assess a company, product, team, project or person for a strategy, business-plan, marketing or coursework slide; use Porter's five forces (create_five_forces) for the pressures on a whole industry, a Harvey ball matrix to score options against criteria, and an issue tree to break one problem down. Only `strengths` is required (an empty [] is fine), but fill all four; infer 3–5 bullets each from context rather than asking. Limits: 8 bullets per quadrant of about 3–8 words, a conclusion of one sentence. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `colors` (object): Optional colour overrides per quadrant, as hex, e.g. { "threats": "#b91c1c" }. Each colours that quadrant's stripe, letter, bullet dots and tint. Default: emerald, amber, sky and red (or the brand pa… - `conclusion` (string): Optional one-line takeaway shown in a muted band under the grid, e.g. "Lead with wholesale to offices; fund a second roaster first". Wraps to 2 lines. Omit for none. - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `labels` (boolean): Show the axis labels: "Helpful" and "Harmful" over the columns, "Internal" and "External" beside the rows. Default true. - `opportunities` (array): External, helpful: trends or openings the subject could use, e.g. ["Offices restocking coffee after hybrid return"]. 0–8 short phrases. Bottom-left quadrant. Default []. - `palette` (array): Hex colours. With the default palette the quadrants are emerald (S), amber (W), sky (O) and red (T); pass brand colours and they apply in order S, W, O, T instead. Default: indigo, sky, emerald, ambe… - `strengths` (array, required): Required (may be empty []). Internal, helpful: what the subject does well or owns, e.g. ["Award-winning single-origin range", "Loyal café following"]. 0–8 short phrases of about 3–8 words; long ones… - `subject` (string): Optional subject of the analysis, e.g. "Northside Roasters, FY26", shown small and muted in the title row's right corner (or above the grid when the title is long). Omit for none. - `threats` (array): External, harmful: what could hurt the subject, e.g. ["Green coffee prices at a 40-year high"]. 0–8 short phrases. Bottom-right quadrant. Default []. - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `weaknesses` (array): Internal, harmful: what holds the subject back, e.g. ["One roaster, near capacity"]. 0–8 short phrases. Top-right quadrant. Default []. - `width` (integer): Chart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the content. ### `create_decision_tree` (~785 tokens) Two Minute Decision Tree Generate a slide-deck-quality decision tree drawn left to right in clean columns of rounded boxes, in the decision-analysis convention: a square where a decision splits into options, a circle where chance splits into events, and a triangle at each end outcome. Branch lines carry an optional `label` ("Yes", "No", an option) and, under a chance node, the probability ("Strong demand · 60%"); end outcomes can carry a numeric `payoff`, lined up in a column at the right (`prefix` "$", `suffix` "m"). Expected values are rolled back automatically once the tree has payoffs and probabilities: every decision and chance node shows its EV, each decision's best option is drawn in the accent colour and the rejected ones are muted with a ‖ prune mark; probabilities that don't add up to 100% are warned about and drawn as given. Node types are inferred (branches with probabilities make a chance node, no branches an outcome, otherwise a decision), so a plain yes/no troubleshooting or eligibility flowchart is just questions with "Yes"/"No" labels and no numbers. Choose it for choosing between options under uncertainty (launch, invest, build vs buy, litigate or settle), expected-value and decision-analysis homework, and yes/no question flowcharts; use an issue tree instead to break a problem or metric into its parts, a chevron process for steps in order, and a Harvey ball matrix to score options against criteria. Limits: 5 levels including the root, up to 5 branches per node, 40 nodes; keep names to a few words. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `palette` (array): Hex colours: the first marks decisions and the best options, the second chance events, the third end outcomes. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald. - `prefix` (string): Text before every payoff and expected value, e.g. "$", "€" or "£". Default none. - `root` (required): The first decision or question, on the left (e.g. "Launch strategy for Atlas" or "Does the laptop power on?"), with its branches nested in `children`. Limits: 5 levels in total including the root, up… - `showEV` (boolean): Roll back expected values: print "EV" on every decision and chance node, draw each decision's best option in the accent colour and mark the rejected options with a ‖ prune mark. When omitted it is on… - `suffix` (string): Text after every payoff and expected value, e.g. "m", "k", "bn" or " pts". Default none. - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x. ### `create_raci` (~798 tokens) Two Minute RACI Matrix Generate a slide-deck-quality RACI matrix (responsibility assignment matrix): tasks or deliverables as rows, roles or teams as columns, and each cell a rounded letter chip, R Responsible, A Accountable, C Consulted or I Informed, with "A/R" for an owner who also does the work and `model: "RASCI"` adding S for Support. Rows can be grouped into phases with `type: "section"` rows; a legend explains the letters. With `checks` (default on), tasks without exactly one A or without an R get an amber note at the row end ("No A", "2 As", "No R") and every broken rule is returned in `warnings`; give every task exactly one A and at least one R unless the user's data says otherwise. Choose it for project roles and responsibilities, PMO governance, onboarding and handover plans, and any "who does what" slide; use a Harvey ball matrix instead to score options against criteria, an org chart for reporting lines, and a timeline when the point is when work happens. Limits: 1–10 roles and up to 30 rows (tasks plus sections); keep task names to a short verb phrase and roles to a job title. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `checks` (boolean): Check the RACI rules: every task has exactly one A and at least one R (A/R counts as both), and every role is R or A on some task. Tasks that break a rule get an amber dot and a short note ("No A", "… - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `legend` (boolean): Show a legend row under the matrix explaining each letter. Default true. - `model` (string): "RACI" (Responsible, Accountable, Consulted, Informed) or "RASCI", which adds S for Support. Sets the legend and the builder's click cycle; an S in a RACI chart is still drawn and added to the legend… - `palette` (array): Hex colours: the first fills R chips, the second tints C chips, the third tints S chips (A is always dark and I light gray, so the letters stay distinct). Pass the user's brand colours here when they… - `roles` (array, required): Column headings, left to right: the roles, teams or people, e.g. ["Project manager", "Dev lead", "Design", "Legal"]. 1–10 roles, up to 30 characters each; long names wrap onto up to three lines. Pref… - `tasks` (array, required): The rows, top to bottom (1–30): tasks, deliverables or decisions, each with one cell per role. A row with "type": "section" is a full-width phase heading (e.g. "Discovery") that groups the tasks belo… - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the content. ### `create_stop_start_continue` (~887 tokens) Two Minute Stop Start Continue Generate a slide-deck-quality Stop Start Continue chart: three equal columns, Stop (red, a stop-sign marker), Start (emerald, a play marker) and Continue (sky, a circular-arrow marker), each a softly tinted panel with up to 8 bullets, plus an optional subject ("Sprint 14 retro") and an optional conclusion band for the agreed actions. Set `order: "start-stop-continue"` when the user puts Start first; rename columns with `labels` (e.g. { "continue": "Keep doing" }). Choose it for sprint and project retrospectives, team or manager feedback, and reviews of a process, project or habit; use create_swot for a strategic assessment of a company or product, a Harvey ball matrix to score options against criteria, and a mind map for an open-ended brainstorm. All three lists are optional, but fill all three; infer 3–5 bullets each from context rather than asking. Limits: 8 bullets per column of about 3–8 words, column names of 1–3 words, a conclusion of one sentence. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown. Input parameters: - `colors` (object): Optional colour overrides per column, as hex, e.g. { "stop": "#b91c1c" }. Each colours that column's stripe, marker, bullet dots and tint. Default: red, emerald and sky (or the brand palette). - `conclusion` (string): Optional one-line takeaway or list of agreed actions shown in a muted band under the columns, e.g. "Actions: Sam sets up review rules by Friday; Priya books the support demo". Wraps to 2 lines. Omit… - `continue` (array): What to keep doing: what works and should carry on, e.g. ["Daily stand-up at 9:30", "Blameless incident reviews"]. 0–8 short phrases. Always the last column. Default []. - `credit` (boolean): Shows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding). - `labels` (object): Optional column names in place of the standard Stop, Start and Continue, e.g. { "continue": "Keep doing" }. An empty or missing name shows the standard one. Up to 30 characters; 1–3 words read best. - `order` (string): Column order: "stop-start-continue" (default) or "start-stop-continue". Continue is always last. Match the order the user writes. - `palette` (array): Hex colours. With the default palette the columns are red (Stop), emerald (Start) and sky (Continue); pass brand colours and they apply to the columns left to right instead. Default: indigo, sky, eme… - `start` (array): What to start doing: new practices worth trying, e.g. ["Pair on risky stories", "Demo to support every sprint"]. 0–8 short phrases. Default []. - `stop` (array): What to stop doing: habits or practices that waste time or hurt results, e.g. ["Merging without code review", "Status meetings with no agenda"]. 0–8 short phrases of about 3–8 words; long ones wrap t… - `subject` (string): Optional subject of the review, e.g. "Sprint 14 retro" or "Q3 onboarding review", shown small and muted in the title row's right corner (or above the columns when the title is long). Omit for none. - `title` (string): Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. - `width` (integer): Chart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the content. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-twominutetoolkit-toolkit/www#diagnostics ## Score history - 2026-11-05: 76 - 2026-11-04: 75 - 2026-11-03: 75 - 2026-11-02: 74 - 2026-11-01: 74 - 2026-10-31: 73 ## Common questions ### What is the Two Minute Toolkit MCP server? Two Minute Toolkit is an MCP server listed in the public MCP registry as com.twominutetoolkit/toolkit. 20 slide-ready chart tools: Gantt, SWOT, 2×2, RACI, org chart, mind map, fishbone. Free. This page covers its hosted endpoint (https://www.twominutetoolkit.com/mcp). ### Is the Two Minute Toolkit MCP server safe to use? Two Minute Toolkit scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the Two Minute Toolkit MCP server expose? Two Minute Toolkit exposes 20 tools: create_timeline, create_harvey_matrix, create_process, create_org_chart, create_mind_map, and 15 more. Their descriptions and schemas cost roughly 14,617 tokens of context every time the server is loaded. ### Does the Two Minute Toolkit MCP server require authentication? No. We connected to Two Minute Toolkit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the Two Minute Toolkit MCP server still maintained? Two Minute Toolkit is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What did VerifyMCP test on the Two Minute Toolkit MCP server? VerifyMCP ran 13 checks on Two Minute Toolkit, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - Remote endpoint: https://www.twominutetoolkit.com/mcp - Website: https://www.twominutetoolkit.com/mcp-docs - Changelog RSS feed: https://verifymcp.io/servers/com-twominutetoolkit-toolkit/www.xml - Changelog JSON feed: https://verifymcp.io/servers/com-twominutetoolkit-toolkit/www/changelog.json - Trust report (JSON): https://verifymcp.io/servers/com-twominutetoolkit-toolkit/www.json - HTML version of this page: https://verifymcp.io/servers/com-twominutetoolkit-toolkit/www