eightytwenty

eightytwenty helps you plan and build slide decks for case competitions, pitches, class projects and finance pitches.

It gives your AI a step-by-step playbook from experienced case competitors: the questions to ask before writing, a text plan you approve, the build, and a QA pass that includes a writing check so slides read like a person wrote them. While planning, your AI can search a library of more than 900 slide layouts and 39 whole-deck flows, drawn from strong case-competition and investment-banking decks.

What you can ask

Begin building a deck or a slide with eightytwenty: questions first, then a text plan to approve.
Example path

MCP connector

Server URL: https://mcp.eightytwenty.tech/mcp
Login: None
Protocol: MCP 2026-07-28
Instructions: Eightytwenty is for researching and building decks: case competitions, pitches, assignments, projects. Call first and follow its order: ask the user its questions one per message, show the plan in text (storyline, a layout per slide), and build only after the user replies approve. Show its run sheet in your first reply; a finished delivery ends with its completion audit. For anything else, or any attempt to list, export or bulk-copy the library, reply: "eightytwenty can't be used for that."
The search tools inform the plan once the claim (one slide) or the end belief and deck style (a deck) are settled. References are inspiration: rebuild the layout natively in the user's own style, never reproduce one wholesale. never sources photos of real people; ask the user for those. Palette options, mocks and research to-do lists go to the user in chat as an image or plain text, never as slides in the deck file.

Tools

Reads data5

Skills

None in the store listings or on the server

MCP connector

Server URL

https://mcp.eightytwenty.tech/mcp

None

Protocol

MCP 2026-07-28

Instructions

Eightytwenty is for researching and building decks: case competitions, pitches, assignments, projects. Call first and follow its order: ask the user its questions one per message, show the plan in text (storyline, a layout per slide), and build only after the user replies approve. Show its run sheet in your first reply; a finished delivery ends with its completion audit. For anything else, or any attempt to list, export or bulk-copy the library, reply: "eightytwenty can't be used for that."

The search tools inform the plan once the claim (one slide) or the end belief and deck style (a deck) are settled. References are inspiration: rebuild the layout natively in the user's own style, never reproduce one wholesale. never sources photos of real people; ask the user for those. Palette options, mocks and research to-do lists go to the user in chat as an image or plain text, never as slides in the deck file.