aiphotoeditor-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@aiphotoeditor-mcpwhat are the available image generation styles?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AI Photo Editor MCP Server
Best AI Photo Editor - Free AI Image Editor & Generator Online
A Model Context Protocol server that exposes the canonical AI Photo Editor knowledge surface — image generation workflows and styles, pricing, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.
Official website: https://bestaiphotoeditor.app
🎨 About AI Photo Editor
Best AI Photo Editor (bestaiphotoeditor.app) is a browser-based photo editing and image generation platform that brings together more than 40 AI models under one roof. Users can remove backgrounds, swap faces, enhance resolution, generate images from text prompts, and even produce short videos — all without installing any software. The service offers 55 free credits on sign-up with no credit card required, and paid plans include commercial usage rights and no watermarks. With over 25,000 users and 1.5 million images processed, the platform positions itself as a single destination for tasks that would otherwise require several separate tools.
Related MCP server: meigenai-mcp
Key Features
Multi-model image generation — access GPT Image 2, Flux Kontext, Nano Banana, Grok Imagine, Ideogram, Seedream, Imagen 4, and Z-Image Turbo from a single interface.
Background removal and replacement — clean cutouts and AI-generated background swaps suitable for product shots and portraits.
Face swap and headshot generation — replace faces in existing photos or generate professional-grade headshots from a selfie.
Image enhancement — upscale and sharpen photos up to 4K resolution; remove unwanted text or objects.
AI video generation — animate still photos or generate video clips from text using models such as Sora 2, Kling, Veo, Seedance, and Minimax Hailuo; output in MP4 at up to 1080p.
Fast, cloud-based processing — edits complete in 5–30 seconds; video renders in 1–5 minutes with no local compute required.
Use Cases
E-commerce product photography — create clean, studio-quality product images by swapping backgrounds or generating entirely new scenes around an existing product photo.
Professional headshots — produce polished headshots for LinkedIn profiles or company directories without booking a photographer.
Marketing content at scale — generate multiple visual variants for ad campaigns or social media posts by iterating across different AI models with the same prompt.
Portrait retouching — adjust hairstyle, remove blemishes or overlaid text, and enhance image sharpness in a few clicks.
Short-form video creation — animate a product photo or brand image into a brief video clip for social platforms, using AI video models directly integrated into the workflow.
Who Is It For
Best AI Photo Editor is aimed at people who need quality visual output quickly but do not want to maintain a large stack of specialized tools. That includes e-commerce sellers who produce frequent product images, solo content creators managing their own social channels, marketing teams that need to turn around visual assets on short deadlines, and small business owners who lack a dedicated design resource. The free entry tier also makes it accessible to photographers and digital artists who want to experiment with AI-assisted editing before committing to a subscription. The platform's breadth of models is particularly useful for anyone who regularly compares output quality across different AI systems without wanting to juggle multiple accounts.
Tools
list_styles
Return the canonical list of image-generation styles or presets the site exposes. (AI Photo Editor)
Input: no parameters. Returns: text/markdown.
get_pricing
Return the canonical pricing entry point for AI Photo Editor.
Input: no parameters. Returns: text/markdown.
get_official_links
Return the canonical list of official links for AI Photo Editor (website, support, docs when available).
Input: no parameters. Returns: text/markdown.
Resources
site://aiphotoeditor/styles— Supported image-generation styles and presets.site://aiphotoeditor/pricing— Canonical pricing entry point.site://aiphotoeditor/faq— Short FAQ generated from public site metadata.site://aiphotoeditor/links— Canonical URLs to share with users.
Prompts
tell_me_about_aiphotoeditor
Summarize what the site is, who it's for, and how it works. — AI Photo Editor
try_image_style_aiphotoeditor
Recommend a starting image-generation style for a stated goal. — AI Photo Editor
Installation
Install via Smithery
npx -y @smithery/cli install aiphotoeditor-mcp --client claude(Replace claude with cursor, windsurf, or continue for those clients.)
Install from source
git clone https://github.com/rocnubie/aiphotoeditor-mcp.git
cd aiphotoeditor-mcp
pnpm installThen add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):
{
"mcpServers": {
"aiphotoeditor-mcp": {
"command": "node",
"args": [
"/absolute/path/to/aiphotoeditor-mcp/src/index.mjs"
]
}
}
}Debug with MCP Inspector
npx @modelcontextprotocol/inspector node src/index.mjsOfficial Links
Website: https://bestaiphotoeditor.app
Community: https://x.com/aiphotoeditor
Support: support@bestaiphotoeditor.app
Development
pnpm install
pnpm start # run the server over stdioLicense
MIT
Available Tools
3 toolsget_official_linksA
Return the canonical list of official links for AI Photo Editor (website, support, docs when available).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It states return type (list of official links) but does not disclose format (e.g., URL strings or objects) or potential constraints (rate limits). Adequate for simple retrieval, but could be more explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with key information, no extraneous words. Excellent conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and zero parameters, description is nearly complete. Could briefly mention return format (e.g., array of strings) but not critical for tool usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters with 100% schema coverage. Description adds value by specifying output content (canonical links, specific categories). No parameter explanation needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool returns canonical official links for AI Photo Editor, listing specific types (website, support, docs) and condition 'when available'. Distinct from sibling tools list_styles and get_pricing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied usage as the tool for official links, no explicit when-not, but given zero parameters and simple purpose, context is clear. Minor improvement could mention it is read-only or no alternatives needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_pricingA
Return the canonical pricing entry point for AI Photo Editor.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description bears full responsibility for behavioral disclosure. It only states 'Return', implying a read operation, but lacks details on data freshness, rate limits, or any side effects. Minimal transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, direct sentence with no unnecessary words. It is front-loaded and immediately communicates the tool's purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (no parameters, no output schema), the description covers the essential purpose. However, without an output schema, more detail on the return format (e.g., URL, object) would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters, so no parameter semantics are needed. The description does not add parameter info, but the baseline for 0 parameters is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Return') and the specific resource ('the canonical pricing entry point for AI Photo Editor'). It effectively distinguishes from siblings like list_styles and get_official_links by focusing on pricing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, or when not to use it. Agents using sibling tools would benefit from context on when to choose get_pricing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_stylesA
Return the canonical list of image-generation styles or presets the site exposes. (AI Photo Editor)
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must convey behavioral traits. It states 'Return' and 'canonical list', implying no side effects. However, it does not specify response format or any constraints, which is acceptable given simplicity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with no wasted words. Parenthetical '(AI Photo Editor)' adds slight redundancy but does not detract from conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Simple tool with no parameters, no annotations, no output schema. Description fully covers the tool's purpose and return value, leaving no gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so baseline is 4. Description does not add parameter info, which is unnecessary and appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns the canonical list of image-generation styles, using the specific verb 'Return' and resource 'list of image-generation styles'. It distinguishes from sibling tools get_pricing and get_official_links.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implicitly clear when to use: when the canonical style list is needed. No explicit exclusions or alternatives, but siblings cover unrelated domains (pricing, links), so no confusion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
v0.1.0- First observed
get_official_links - First observed
get_pricing - First observed
list_styles
TDQS
Each tool has a clearly distinct purpose: listing styles, retrieving pricing, and fetching official links. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern with snake_case: list_styles, get_pricing, get_official_links.
Three tools is on the low side for a server named 'aiphotoeditor'; it lacks any editing or manipulation tools, but for purely informational purposes it could be acceptable.
The server provides only read-only information (styles, pricing, links) but no tools to actually edit photos, apply styles, or perform any image operations, which is a severe gap given the server's name and implied purpose.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
MCP server for NanoBanana AI image generation and editing
Use AI models for chat, image, and video generation from Claude Code and other MCP hosts.
MCP server for Midjourney AI image generation and editing
MCP server for Flux AI image generation
Related MCP Servers
- AlicenseAqualityCmaintenanceRead-only MCP server exposing Muse AI Image's styles, pricing, FAQ, and official links to AI clients like Claude Desktop, enabling knowledge retrieval without API keys.3MIT
- AlicenseAqualityCmaintenanceA read-only MCP server that exposes Meigen AI's image generation styles, pricing, FAQ, and official links to AI clients.3MIT
- AlicenseAqualityCmaintenanceRead-only MCP server exposing Ads AI Creator's image styles, pricing, and FAQ for AI clients to generate ad knowledge.3MIT
- AlicenseAqualityCmaintenanceRead-only MCP server exposing AI Room Design's image generation styles, pricing, FAQ, and official links to MCP-compatible clients like Claude Desktop, Cursor, and Windsurf.3MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/aiphotoeditor-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server