NinjaChat MCP

ai.ninjachatPublished by ninjachat.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Create images & video from any MCP agent — 17 models, spend limits, one URL.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant generate images and video through NinjaChat's 17 models, with spend limits and a single URL.

What you can do
  • Generate images and video from an MCP-capable agent using NinjaChat's model lineup.
  • Choose among 17 image and video models through one endpoint.
  • Apply spend limits to control how much generation is allowed.
  • Connect from desktop or web-based clients over a single remote URL.
When to use it
Useful when you want an assistant to produce images or short video without wiring up separate model providers, and you want generation spending capped by a limit.
Requirements
A remote MCP endpoint at the provider's site; no local package. Authentication is required: OAuth for Claude and ChatGPT, or a Bearer API key sent in the Authorization header for clients such as Cursor, Claude Code, Codex and VS Code. A NinjaChat account is implied.
Before you install
The Authorization header carries a secret API key; keep it out of shared configs and logs. Image and video generation may consume paid credits, so check the spend limits before use. Prompts and generated content are sent to the provider.

Installation

In SourceWeft

  1. Open NinjaChat MCP 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/ai.ninjachat%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": {
    "ninjachat": {
      "type": "http",
      "url": "https://www.ninjachat.ai/api/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.