VixAI Connect

app.vixaiPublished by vixai.appOfficial publisherv1.0.0Updated Oct 24, 2026

Create, review, publish and schedule Instagram images, carousels and Reels with AI assistants.

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

VixAI Connect is a remote MCP server that lets an AI assistant create, review, publish and schedule Instagram images, carousels and Reels.

What you can do
Create Instagram images, carousels and Reels with an AI assistant, per the registry description. Review drafted content before it goes out. Publish content to Instagram. Schedule posts for later. No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you want an assistant to help produce and manage Instagram content end to end, from drafting visuals and carousels to publishing or scheduling posts, rather than only writing captions.
Requirements
A remote MCP endpoint at mcp.vixai.app over streamable HTTP. OAuth authentication is required, so a VixAI account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
Publishing and scheduling act on a live Instagram account and can make content public, so review before approving. Access is granted through OAuth to your VixAI account; check which permissions the sign-in requests. Content you submit is sent to VixAI's service.

Installation

In SourceWeft

  1. Open VixAI Connect 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.vixai%2Fvixai-connect/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": {
    "vixai-connect": {
      "type": "http",
      "url": "https://mcp.vixai.app/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.