AIGE

ws.aigePublished by aige.wsOfficial publisherv1.0.2Updated Oct 26, 2026

AI creative studio for images, video and carousel decks, with one saved character in every shot.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP endpoint for AIGE, an AI creative studio that generates images, video and carousel decks with one saved character kept consistent across shots.

What you can do
  • Generate images, video and carousel decks from an AI creative studio.
  • Keep one saved character consistent across every generated shot.
  • Connect over a remote streamable HTTP endpoint with OAuth sign-in.
  • No tool list is published, so the exact operations are not documented here.
When to use it
Worth adding when you want an assistant to produce visual creative assets — images, short video or carousel decks — that feature the same recurring character rather than unrelated one-off generations.
Requirements
A remote MCP endpoint at aige.ws over streamable HTTP; no local package or runtime. OAuth authentication is required, so an AIGE account and a browser-based sign-in flow are needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your AIGE account, so review the scopes requested during sign-in. Generation likely consumes paid credits or quota on the AIGE service, and prompts plus any uploaded character material are sent to that third party. The tool list is not published, so confirm what it can create or change before relying on it.

Installation

In SourceWeft

  1. Open AIGE 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/ws.aige%2Fantix/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": {
    "aige": {
      "type": "http",
      "url": "https://aige.ws/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

3
  1. v1.0.2LatestOct 26, 2026
  2. v1.0.1Oct 21, 2026
  3. v1.0.0Sep 21, 2026

Score

83% 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
  • 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.