Koskamo

ViNano MCP

An official remote MCP server by ViNano AI that allows agents to generate and edit images and create videos using models like GPT Image 2.5 and Veo 3.1. It provides tools to list models, check credit balances, quote prices before generation, and fetch finished assets, with OAuth authentication and credit-based billing.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

ViNano MCP logo, by ViNano AIVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by ViNano AI
You need:Accounts that have completed any purchase (a credit pack or a plan) can connect.Existing Team subscriptions and API allowlist accounts keep their access.Clients that support remote MCP servers over Streamable HTTP with OAuth sign-in.
MCP endpoint (Streamable HTTP)
https://mcp.vinano.ai/api/mcp
Vendor documentation

What you can do with it

  • Generate images from text prompts
  • Edit uploaded images with text instructions
  • Create videos from text or images
  • Check credit balance and task status

Source and maintenance

Vendor evidenceRegistry 0.2.0

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
394 ms
95th percentile latency
394 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 394 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http vinano-mcp https://mcp.vinano.ai/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add vinano-mcp --url https://mcp.vinano.ai/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vinano-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "vinano-mcp": {
      "url": "https://mcp.vinano.ai/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "vinano-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.vinano.ai/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vinano-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "vinano-mcp": {
      "type": "http",
      "url": "https://mcp.vinano.ai/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http vinano-mcp https://mcp.vinano.ai/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "vinano-mcp": {
      "url": "https://mcp.vinano.ai/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "vinano-mcp": {
      "serverUrl": "https://mcp.vinano.ai/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like ViNano MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run ViNano MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing