Overview
Automette runs an MCP server. Connect an AI assistant to it and the assistant can do the things you would otherwise do by hand or by writing code: design a template, render documents, wire up a webhook, create a Dynamic URL.
https://automette.com/api/mcpWhat this is for
The assistant does the work in your account, with your data. You ask for an outcome and it uses the tools rather than telling you which buttons to press.
Connect
Two ways in: a personal sign-in, or an API key.
Tools
All 28, grouped by what you would ask for.
What to ask for
Worked examples, and what to expect back.
Troubleshooting
When it will not connect, or picks the wrong team.
What it is not
Not our AI. Nothing on this server calls a model of ours. The assistant you connect is the one doing the thinking, using its own intelligence against our tools. That is deliberate: bring a frontier model and you get frontier results, rather than being capped by whatever we chose to run.
Not a way around the rules. Everything an assistant does goes through the same service layer as the dashboard and the REST API — the same team scoping, the same plan limits, the same credit accounting. A tool cannot do something the API would refuse.
What it knows
The server carries our own reference material and hands it over on request: the Typst and canvas skills, the component and property tables, the font catalogue, and a set of worked patterns. An assistant that has never seen Automette can read what it needs mid-task rather than guessing at our template format.
That is why an assistant connected here writes better templates than one you paste an example into: it can look things up.
Last updated on