Connect an agent over MCP or a script over the REST API. Pages go live from your editor or your CI; newsletters and social posts come back to you as drafts.
> Turn CHANGELOG.md into a release notes page on the docs site and publish itaveiro_list_sites → docs.example.comaveiro_create_page → /changelog/2-4aveiro_publish_site → live> Now draft the newsletter and a LinkedIn post about itaveiro_newsletter_create_draft → waiting for youaveiro_social_create_draft → waiting for approval
scope: publish:write2 drafts for you to review
41MCP tools across sites, pages, media, email and social
11API token scopes, granted one at a time
2Ways to connect an agent: OAuth or a personal token
THREE WAYS IN
Your editor, your pipeline, or the dashboard
All three reach the same sites, pages and drafts. Use whichever fits the task in front of you.
MCP server
A remote MCP server at aveiro.app. Connect Claude, ChatGPT, Cursor or any MCP client with OAuth or a personal token, and it can work on sites, pages, collections, media, newsletters, social posts and mockup videos.
REST API
The same operations under /api/v1, for scripts and CI. Tokens carry scopes, so a build job can hold publish:write and nothing else.
Quasar in the dashboard
The assistant inside Aveiro uses the same tools from the dashboard, the site editor and the campaign editor — for when you'd rather describe a change than click through it.
GUARDRAILS
What an agent can do, and what stays with you
A published page can be edited or taken down, so an agent may publish one. An email to your list and a post in your name can't be taken back, so those stop at a draft.
Action
Agent over MCP
You
Create and edit pages
Yes
Yes
Publish a site
Yes, with publish:write
Yes
Newsletter
Writes the draft
Sends or schedules it
Social posts
Writes the draft, proposes a time
Approves, then it's scheduled
Screenshots and mockup videos
Yes
Yes
An agent's permissions come from the scopes on its token or the OAuth grant you approve. Revoke either from the dashboard at any time.
ON A SCHEDULE
Queued sends that run without you watching
Once you've approved something, it goes out on time whether or not you're at a desk.
Campaigns send at the time you set, and a large send can be paced
Approved social posts publish at their scheduled time on each network
A campaign can be resent to the people who didn't open it
ON PUBLISH
Published for readers and for models
Every publish ships the parts search engines and AI assistants read — no plugin, no build step.
A live address from the first publish
Every site gets an aveiro.page URL straight away. Point your own domain at it whenever you're ready.
Locales as real content
Publish a separate version of a page per locale, with a language switcher on the site — content you control, not a machine pass.
llms.txt and Markdown pages
Published sites expose llms.txt and a Markdown version of each page, so an assistant reads structured text instead of scraping HTML.
Metadata without the checklist
Titles, descriptions, canonicals, OpenGraph and structured data are generated from each page.
Any client that supports remote MCP servers over HTTP — Claude, ChatGPT, Cursor and others. Add https://www.aveiro.app/api/mcp/mcp and sign in, or use a personal token.
Can an agent send my newsletter or post to social?
No. Over MCP and the API it can write and update drafts, and for social posts it can propose a time. Sending a campaign and approving a post are things you do.
Can I publish from CI?
Yes. Create a token with only the scopes the job needs — for example content:write and publish:write — and call the REST API from your pipeline.
Is there a GitHub integration?
There's no repository sync. Agents and scripts publish through MCP or the REST API, which covers the same ground from wherever your code runs.