Runs Cults3D GraphQL queries and mutations, checks approved sharing origins, and builds a pre-filled publish link for a 3D file.
3actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro checks Cults sharing configuration and approved origins to diagnose 3D file publication issues. Origin validation prevents blocked publishing due to misconfiguration.
Ayro generates a direct one-click share URL for publishing 3D files to the Cults community in French locale. Shared links bypass manual upload steps for faster distribution.
Ayro executes GraphQL queries and mutations against the Cults3D API to programmatically manage 3D model data and publishing workflows. Advanced operations are enabled through direct API access.
Each card is one request a support team gets, and the Cults actions Ayro runs to close it.
Ayro queries the Cults3D API for design, designer and own-sales metadata, checks whether the sharing origin is approved, and builds a share URL with the file already filled in.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Cults actions it has and picks the ones a request needs.
Authorize the Cults 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 Cults 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 freeCults · Ayro
What can you do in Cults 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 Cults.
Cults approves sharing origins manually through support before the Share on Create feature works for a site. Get Approved Origins tries to read that detail off the creation page and can legitimately come back empty, so Ayro reports what it found and points to Cults support at cults3d.com/en/api rather than treating an empty result as approval.
All 3 actions your agent can call on Cults, straight from the live MCP connection.
Inspects the Cults creation page to detect any sharing origin information.
Execute GraphQL queries and mutations against the Cults3D API.
Generate a one-click share URL for publishing a 3D file to Cults (French locale).
Same connection, same setup. Pick the next one your team already uses.
Generates alt text for one image or a whole page of them, searches the library by keyword, and corrects entries as images change.
Turns a written brief into a DreamStudio generation, guides it with a reference image, and checks which engines and credits the key has left.
Lists the design templates available on an Imejis.io account so a team can confirm which layouts exist, and their exact names, before requesting a render.
Searches Mobbin's screen library in plain language and returns matching screens inline, with app names and links back to Mobbin.
Generates the Plasmic globalContexts snippet so a developer gets working code instead of a documentation link.
Publishes CMS items and whole sites, fixes page SEO metadata, fulfills or refunds store orders, and reads the form submissions a site collected.

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