Imaginepro Mcp Server

Created By
ImaginePro8 months ago
Overview

What is ImaginePro MCP Server?

ImaginePro MCP Server is a fast and powerful Model Context Protocol server that integrates ImaginePro's AI image and video generation capabilities into various AI assistants, enabling seamless creative content generation through natural language.

How to use ImaginePro MCP Server?

To use the ImaginePro MCP Server, you need to install it via npm or npx, configure it with your ImaginePro API key, and integrate it with compatible AI tools like Claude.

Key features of ImaginePro MCP Server?

  • Text-to-Image Generation: Create stunning AI images from text descriptions.
  • Video Generation: Generate smooth video animations from start and end frames.
  • Image Upscaling: Enhance image resolution and quality.
  • Multi-modal Generation: Combine text and images for advanced generation.
  • Real-time Progress Updates: Monitor the status of generation tasks in real-time.

Use cases of ImaginePro MCP Server?

  1. Generating photorealistic images from descriptive prompts.
  2. Creating video transitions between two images.
  3. Enhancing image quality through upscaling.
  4. Editing images using inpainting techniques.

FAQ from ImaginePro MCP Server?

  • What is required to run the server?

You need Node.js (>= 18.0.0) and an ImaginePro API key.

  • Is there a quick way to install it?

Yes! You can use npx for a quick install without needing to set up globally.

  • Can I use it with other AI tools?

Yes! It works with various MCP-compatible tools like Claude.

Server Config

{
  "mcpServers": {
    "imaginepro": {
      "command": "npx",
      "args": [
        "-y",
        "imaginepro-mcp-server"
      ],
      "env": {
        "IMAGINEPRO_API_KEY": "sk-your-api-key-here"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
ImaginePro
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago