Media · Remote MCP server
Pixapi
MCP server for Pixapi: check live credit pricing and balance, then generate images and video.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Pixapi-AI/pixapi-mcp- Version
- 0.1.4
- Status
- Active
- Category
- media
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-08
- Updated
- 2026-09-08
- Publisher
- Pixapi-AI (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Pixapi-AI) · how
- Website
- pixapi.ai
- Repository
- github.com/Pixapi-AI/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.pixapi.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | pixapi-mcp | 0.1.4 | stdio |
How to connect Pixapi
Pixapi is a remote MCP server: there is nothing to install. Its endpoint is https://api.pixapi.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: pixapi-mcp version 0.1.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y pixapi-mcp@0.1.4.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"pixapi-mcp": {
"command": "npx",
"args": [
"-y",
"pixapi-mcp@0.1.4"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More media servers
| Server | Runs |
|---|---|
| PitchGhostAI-powered social listening across Twitter, LinkedIn, Reddit, Facebook, and more. | Remote · HTTPLive check: sign-in required |
| Pith - Instagram publishingPublish to Instagram from chat - official Graph API, OAuth 2.1, free for your own posts. | Remote · HTTPLive check: sign-in required |
| PitstopF1 MCP server: live timing, telemetry, standings, news, and a queryable 1950-present database. | Local · stdio |
| Pixabay MCP ServerUnofficial MCP server for the Pixabay API: search and fetch royalty-free images and videos. | Local · stdio |
| Pixel AgentConvert images to PNG, JPEG, WebP, or AVIF through one public remote MCP tool. | Remote · HTTPLive check: ✓ handshake |
| Pixel SurgeonAI image and video generation, editing, and region repair via Gemini, OpenAI, and Grok. | Local · stdio |
| PixelDojoGenerate images, video, audio and short films with 140+ AI models from any MCP client. | Remote & Local · HTTP, stdioLive check: sign-in required |
| PixelDriveGenerate branded images at scale: design templates and render them to PNGs by prompt. | Remote · HTTPLive check: sign-in required |