ASMI — AI avatars for your site

tech.broenPublished by broen.techOfficial publisherv1.1.0Updated Oct 25, 2026

Design your site's AI avatar in the ASMI studio; your coding agent ships it into your repo.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

ASMI lets an assistant take an AI avatar designed in the ASMI studio and ship it into your website's repository.

What you can do
Connect an assistant to the ASMI service so it can work with an AI avatar you designed in the ASMI studio and add it to your site's codebase. The manifest lists no individual tools, so the exact operations are not documented here; the stated purpose is moving a designed avatar into your repo.
When to use it
Useful when you have already designed an AI avatar in the ASMI studio and want your coding agent to integrate it into a website repository rather than wiring it up by hand.
Requirements
A remote endpoint at broen.tech over streamable HTTP. OAuth authentication is required, and an ASMI API key (prefix auk_) must be supplied in the x-api-key header; the key is created in the ASMI studio's Deploy dialog. A Bearer token is also accepted.
Before you install
You must supply an ASMI API key, a secret that grants access to your ASMI account; keep it out of shared code and logs. The server writes into your repository, so review the changes it makes before committing. No tool list is published, so confirm what it can change before connecting.

Installation

In SourceWeft

  1. Open ASMI — AI avatars for your site 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/tech.broen%2Fasmi/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": {
    "asmi-ai-avatars-for-your-site": {
      "type": "http",
      "url": "https://broen.tech/api/asmi/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.1.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.