Aveiro

app.aveiroPublished by aveiro.appOfficial publisherv1.0.0Updated Oct 24, 2026

Create, update, and publish real hosted websites from your agent via the Aveiro API.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant create, update, and publish real hosted websites through the Aveiro API.

What you can do
Aveiro is a remote MCP endpoint that connects an assistant to the Aveiro API so it can build and manage hosted websites. According to the registry description, it supports creating, updating, and publishing sites directly from the agent. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when you want an assistant to produce or revise a live website rather than just draft content, for example generating a small site and publishing it without leaving the conversation.
Requirements
A remote MCP endpoint at aveiro.app, reachable over streamable HTTP. Authentication is required via OAuth, so the user needs an Aveiro account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server can create, update, and publish websites, which changes publicly visible content; review what the assistant publishes before it goes live. Access is granted through OAuth to your Aveiro account, so scope the authorization carefully. Site content is sent to Aveiro as a third party.

Installation

In SourceWeft

  1. Open Aveiro in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.aveiro%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "aveiro": {
      "type": "http",
      "url": "https://www.aveiro.app/api/mcp/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.