1. Create an API key
Use Account to create a key with images:write, images:read, and optional text:write.
The MCP wrapper exposes the public API as agent tools so an AI agent can upload, polish, check, and download images inside content, ecommerce, or publishing workflows.
Use Account to create a key with images:write, images:read, and optional text:write.
Run the local Node.js bridge with npm --silent run mcp and pass NOAIVIBE_API_KEY in env.
The agent can upload local files, create jobs, poll status, and download finished images.
Upload a local JPG, PNG, or WEBP file so an agent can create processing jobs without hosting the image first.
POST /api/v1/uploads
Credits: free_upload
Create a NoAIVibe image processing job from a hosted image URL or a local file path uploaded by the MCP bridge.
POST /api/v1/images/jobs
Credits: uses_account_credits
Check queued, processing, completed, or failed status for an image job.
GET /api/v1/images/jobs/{job_id}
Credits: uses_account_credits
Download the completed image result for downstream automation.
GET /api/v1/images/jobs/{job_id}/download
Credits: uses_account_credits
Run the bridge beside your agent. It exposes the tools above to your agent and uses the same API key as the web app.
NOAIVIBE_API_BASE_URL=https://noaivibe.com \
NOAIVIBE_API_KEY=noaivibe_live_... \
npm --silent run mcp
{
"mcpServers": {
"noaivibe": {
"command": "npm",
"args": ["--silent", "run", "mcp"],
"env": {
"NOAIVIBE_API_BASE_URL": "https://noaivibe.com",
"NOAIVIBE_API_KEY": "noaivibe_live_..."
}
}
}
}
The MCP server does not manage billing locally. Your NoAIVibe account handles credits, refunds, and job history.
enhance_image accepts either image_url or file_path. For a local JPG, PNG, or WEBP, the bridge uploads the file first, creates a NoAIVibe job, and returns the job object for polling.