Integrations
Playyy in your AI assistant
Connect Playyy to Claude, ChatGPT, Grok, Cursor, VS Code, or any MCP client. Ask for a deck, a poster, or a set of social graphics, and Playyy's design agent builds editable pages in your account.
https://mcp.playyy.ai/mcpChoose your assistant
Claude
Add Playyy as a connector in Claude.ai, Claude Desktop, or Claude Code.
Setup guideChatGPT
Add Playyy as a custom connector with ChatGPT developer mode.
Setup guideGrok
Bring Playyy into Grok as a custom MCP connector.
Setup guideCursor
Give Cursor's agent Playyy tools through mcp.json.
Setup guideVS Code
Use Playyy from GitHub Copilot agent mode in VS Code.
Setup guideAny other MCP client
Any client that supports remote MCP servers with OAuth sign-in.
RequirementsHow it works
- 1
Add the server
Paste the Playyy server URL into your assistant's connector or MCP settings.
- 2
Sign in and approve
Sign in to Playyy and choose the workspace your assistant may use. No API keys to copy.
- 3
Ask for a design
Describe what you need. Playyy builds it as an editable file you can open, change, and export.
What your assistant can do
Create designs from a brief
Slides, posters, flyers, social graphics, and one-page layouts, built as editable pages in the Playyy editor rather than flat images.
Iterate in conversation
Refine the copy, swap a colour, or rework a single page of a design that's already in progress.
Use your own material
Share a public link to a logo, photo, brief, or spreadsheet and Playyy uses it as reference for the design.
Write documents
Create documents and add, update, or remove headings, paragraphs, lists, and other blocks.
Find and export work
Search your files by title and export designs to PNG, JPG, or PPTX, and sheets to XLSX.
Share with your team
Turn workspace link sharing on or off for a file, with view, comment, or edit access.
Any other MCP client
Playyy works with any client that supports remote MCP servers over Streamable HTTP with OAuth sign-in. Point it at the server URL and complete the browser sign-in when asked. API keys and local (stdio) setups are not supported.
- Transport: Streamable HTTP
- Auth: OAuth 2.1 with dynamic client registration or client ID metadata documents
- Scope: one Playyy workspace per connection
{
"mcpServers": {
"playyy": {
"url": "https://mcp.playyy.ai/mcp"
}
}
}Key names vary by client; most accept a server name and URL.