Browses templates with their layers and tags, creates new ones at set dimensions, and groups them into collections with custom metadata.
11actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro fetches a template by UUID. Support accesses the template configuration for customization or technical review.
Ayro retrieves all templates from the Placid project. Support browses available image templates for customer selection.
Ayro updates an existing Placid template's properties. Support adapts templates for new customer requirements or branding.
Each card is one request a support team gets, and the Placid actions Ayro runs to close it.
Ayro pages through the project's templates 20 at a time, filtered by collection or title, and returns a template's thumbnail, tags and layers so the correct UUID reaches whatever renders the asset.
Ayro creates a Placid template with the dimensions requested plus any tags or custom metadata, then revises its title or tags later without anyone opening the editor.
Ayro creates a collection with its title and custom data, then manages membership by replacing the whole set or adding and removing individual templates as the campaign changes.
Ayro reads a collection's title, custom data and associated template UUIDs back before deleting it, and removes individual templates by UUID once nothing depends on them.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Placid actions it has and picks the ones a request needs.
Authorize the Placid account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Placid actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freePlacid · Ayro
What can you do in Placid without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Placid.
No. The connected actions manage templates and collections; there is no render call in this toolkit. Ayro finds the right template and returns its UUID and layer list, which is what your own rendering request or Placid automation needs to produce the asset.
All 11 actions your agent can call on Placid, straight from the live MCP connection.
Create a new template collection to group multiple templates.
Create a new Placid template.
Delete a template collection by its ID.
Delete a specific template identified by UUID.
Retrieve a single collection by its ID.
Retrieve a list of all template collections.
Retrieve a template by UUID.
List all available templates via the Natural Language API.
Retrieve a list of templates from your project.
Update an existing template collection.
Update an existing Placid template.
Same connection, same setup. Pick the next one your team already uses.
Lists the designs and fonts available in a workspace, groups new work into projects, and confirms credentials before anything depends on them.
Searches the media library by tag or visual similarity, uploads and transforms assets, and keeps folders, tags, and metadata current.
Finds files, reads nodes and comments, posts feedback, extracts design tokens and variables, and renders node images.
Resolves a company name to a verified domain and pulls its logo as PNG or SVG, so records and documents carry the right mark.
Searches stock photos and video, opens saved and featured collections, and returns credits plus the right file size for each asset.
Searches a photographer's images, returns download URLs at the right size, walks the folder tree, and unlocks protected albums.

Authorize the account and your agent has all 11 actions from the first conversation.
