Pictomancer MCP MCP server

Official MCP server for Pictomancer's image optimization API, enabling AI agents to resize, compress, convert, crop, and analyze images via HTTP requests. It supports chaining operations in a pipeline and includes features like AI-generated image processing and provenance detection, with machine-readable discovery and payment capabilities.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Pictomancer

MCP endpoint (Streamable HTTP)

https://api.pictomancer.ai/mcp

Vendor documentation

What you can do with it

Resize and compress images for web delivery
Convert images between formats like JPEG, PNG, and WebP
Chain multiple image operations in a single pipeline request
Analyze image metadata and detect provenance

Tools advertised by the last live check:

get_format_info
estimate_cost
analyze_image
resize_image
compress_image
convert_image
crop_image
optimize_for_vision
optimize_generated_image
image_pipeline

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 a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http pictomancer-mcp https://api.pictomancer.ai/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 pictomancer-mcp --url https://api.pictomancer.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable pictomancer-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "pictomancer-mcp": {
      "url": "https://api.pictomancer.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "pictomancer-mcp": {
      "type": "streamableHttp",
      "url": "https://api.pictomancer.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start pictomancer-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "pictomancer-mcp": {
      "type": "http",
      "url": "https://api.pictomancer.ai/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 pictomancer-mcp https://api.pictomancer.ai/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": {
    "pictomancer-mcp": {
      "url": "https://api.pictomancer.ai/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": {
    "pictomancer-mcp": {
      "serverUrl": "https://api.pictomancer.ai/mcp"
    }
  }
}

See all 782

Do you run Pictomancer 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