Pixelle MCP vs MCP Florence2
A side-by-side look at the Pixelle MCP and MCP Florence2 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Pixelle MCP for multimedia process work as a local process; choose MCP Florence2 for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Pixelle MCP when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PORT.
Choose MCP Florence2 when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You want tools like
src, prompt.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 55/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | PORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,130 | 7 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Pixelle MCP | View MCP Florence2 |
Tools & capabilities
Pixelle MCP tools
No tool names declared yet. Check the project README from the listing page.
MCP Florence2 tools 2
srcA file path or URL to the image file that needs to be processed.promptA custom prompt for the Florence-2 model.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Pixelle MCP
{
"mcpServers": {
"aidc-ai-pixelle-mcp": {
"command": "uvx",
"args": [
"pixelle@latest"
],
"env": {
"PORT": "YOUR_PORT_HERE"
}
}
}
}
MCP Florence2
{
"mcpServers": {
"mcp-florence2": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/jkawamoto/mcp-florence2",
"mcp-florence2"
]
}
}
}
Frequently asked questions
Pixelle MCP is categorized under Multimedia Process and uses a local stdio subprocess. MCP Florence2 belongs to Multimedia Process and uses a local stdio subprocess. Pick Pixelle MCP for multimedia process work and MCP Florence2 for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Pixelle MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. MCP Florence2 has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aidc-ai-pixelle-mcp and mcp-florence2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Pixelle MCP has a quality signal of 55/100 (Good) with 6 views, 0 installs and 1,130 GitHub stars. MCP Florence2 has 52/100 (Good) with 0 views, 0 installs and 7 GitHub stars.