Indian Pixels

io.github.jegaaravindbabuPublished by GitHub account jegaaravindbabuv1.0.0Updated Oct 24, 2026

Generate images, videos, music & lip sync with 200+ AI models (Flux, Veo 3, Kling, Suno)

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Indian Pixels is a remote MCP server that lets an assistant generate images, videos, music and lip-sync content using 200+ AI models such as Flux, Veo 3, Kling,

What you can do
Generate images with AI models such as Flux through the Indian Pixels platform. Create videos with models such as Veo 3 and Kling. Produce music with models such as Suno. Create lip-sync content. Choose among more than 200 AI models for these media generation tasks.
When to use it
Useful when you want an assistant to produce images, videos, music or lip-sync media without wiring up each model provider yourself, and you already have or are willing to create an Indian Pixels account.
Requirements
A remote endpoint at indianpixels.com over streamable HTTP. A required Indian Pixels API key, sent as a bearer token in the Authorization header; the key is created in the Indian Pixels dashboard. Network access is needed.
Before you install
The server requires an API key sent in the Authorization header, so treat it as a secret. Generation on a hosted platform may consume paid credits or quota; check Indian Pixels pricing before use. Prompts and generated media are sent to that third-party service.

Installation

In SourceWeft

  1. Open Indian Pixels 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.jegaaravindbabu%2Findian-pixels/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": {
    "indian-pixels": {
      "type": "http",
      "url": "https://www.indianpixels.com/api/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. v1.0.0LatestOct 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.