Sogni MCP

io.github.Sogni-AIPublished by GitHub account Sogni-AIv0.1.0Updated Nov 6, 2026

Generate and edit images, video, and music with Sogni AI through a hosted MCP connection.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Hosted Sogni AI MCP endpoint that lets an assistant generate and edit images, video, and music through your own Sogni developer API key.

What you can do
  • Generate images, video, and music from prompts via Sogni AI.
  • Edit existing media through the same hosted connection.
  • No tool list is published, so the exact operations are not documented here.
When to use it
When you want an assistant to create or edit visual and audio media with Sogni AI without running a local server, and you already have a Sogni developer API key.
Requirements
A remote streamable HTTP endpoint at mcp.sogni.ai; no local package or runtime. A Sogni Developer API key sent as a bearer token in the Authorization header.
Before you install
The connection requires your own Sogni API key, which is a secret; keep it out of shared logs and configs. Generation may consume paid credits on your Sogni account. Prompts and media are sent to Sogni's hosted service.

Installation

In SourceWeft

  1. Open Sogni MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.Sogni-AI%2Fsogni-mcp/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.

{
  "mcpServers": {
    "sogni": {
      "type": "http",
      "url": "https://mcp.sogni.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestNov 6, 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.