Use Curio with WorkBuddy
WorkBuddy already writes the deck, the report and the summary for you. What it cannot do on its own is make them look like a designer touched them — left alone it reaches for the same default look as every other AI. Hand it a Curio style and the output arrives dressed.
What this gives WorkBuddy
Curio packages established design styles — movements, brands, cultural traditions — as complete machine-readable specs: colour roles, type scale, spacing rhythm, shapes, shadows, motion. WorkBuddy reads one and applies it to whatever it is producing.
There are two ways in. Pasting a share link needs no setup and works today. Connecting the MCP server puts the whole library inside WorkBuddy so it can search for a style mid-conversation.
Connect over MCP
-
1
Open the MCP server settings
In the sidebar open 插件 (Plugins), then click MCP 服务器 (MCP Servers) at the top right.
-
2
Add the Curio server
Click 配置 MCP (Configure MCP) and add an entry named curio with the URL https://mcp.designbycurio.com/mcp.
-
3
Save and authorize
Save, find Curio in the connector list and enable it. Sign in with email, Google or GitHub. Connecting and browsing are free; unlocking a style costs 1 credit, once, and your AI asks you first.
-
4
Ask for a style by name or by feel
Tell WorkBuddy which style to use and what to build. It searches the library, fetches the full spec and produces the deck, report or page in that style.
What you get
Decks and reports that look intentional: one authoritative spec drives colour, type and spacing instead of WorkBuddy guessing per slide.
A named look you can ask for again — the same style applied on Monday still matches the one applied next month.
No design skill required on your side. You pick the style; WorkBuddy does the layout work.
Example prompts
Use this Curio design style for the deck: <paste share link>. Build a 10-slide quarterly review from the notes below.
Search Curio for a calm, editorial style and rewrite this report in it.
FAQ
Do I have to set up MCP to use Curio here?
No. Pasting a share link needs no setup and is the quickest way to try a style. MCP is worth it once you want WorkBuddy to search the whole library on its own.
The MCP setup asks me for a token — what now?
Curio signs you in with OAuth and issues no token to paste, and WorkBuddy's own MCP examples are local command servers, so remote sign-in may not complete on every version. If your build asks for a token, use the share link instead — it delivers the same spec.