piapi-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is piapi-mcp-server?

piapi-mcp-server is a TypeScript implementation of a Model Context Protocol (MCP) server that integrates with PiAPI's API, allowing users to generate media content using various AI tools directly from MCP-compatible applications.

how to use piapi-mcp-server?

To use piapi-mcp-server, clone the repository, install the dependencies, set up your PiAPI API key in a .env file, and run the server. Connect it to compatible applications like Claude Desktop by configuring the appropriate settings.

key features of piapi-mcp-server?

  • Flux Image generation from text descriptions
  • Midjourney Image generation
  • Kling video generation
  • Luma Dream Machine video generation
  • AI song generation with Suno/Udio
  • 3D model generation with Trellis
  • Workflow planning inside LLMs

use cases of piapi-mcp-server?

  1. Generating images from text prompts for creative projects.
  2. Creating videos using AI tools for marketing or educational content.
  3. Developing interactive applications that utilize AI-generated media.

FAQ from piapi-mcp-server?

  • What is required to run piapi-mcp-server?

You need Node.js 16.x or higher, npm or yarn, and a PiAPI API key.

  • Is there a graphical interface for piapi-mcp-server?

No, it is primarily a server-side application that integrates with other MCP-compatible applications.

  • Can I use piapi-mcp-server for commercial purposes?

Yes, as long as you comply with the licensing terms.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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