Mockuuups

Created By
Mockuuupsa year ago
MCP remote server for Mockuuups Studio API. Generate professional mockups directly from AI chat interfaces like Claude, ChatGPT, and automation tools. Streamlines design workflows by eliminating context switching between tools.
Overview

what is Mockuuups?

Mockuuups is a remote server for the Mockuuups Studio API that allows users to generate professional mockups directly from AI chat interfaces like Claude and ChatGPT, streamlining design workflows by eliminating context switching between tools.

how to use Mockuuups?

To use Mockuuups, create a free developer account to obtain an API key, connect it to your AI tool, and start generating mockups by simply asking your AI assistant to create mockups from images or URLs.

key features of Mockuuups?

  • Generate mockups directly from AI chat interfaces.
  • Automate mockup creation in tools like Make.com and Zapier.
  • Supports various devices and scenes for mockup generation.

use cases of Mockuuups?

  1. Designers can quickly create mockups for presentations.
  2. Marketers can generate visuals for social media campaigns.
  3. Developers can integrate mockup generation into their applications.

FAQ from Mockuuups?

  • Can I use Mockuuups with any AI tool?

Yes! Mockuuups is compatible with any MCP-compatible tool like Claude and ChatGPT.

  • Is there a cost to use Mockuuups?

You can start for free with 50 credits after signing up for a developer account.

  • How do I get started?

Sign up at the Mockuuups Developer Portal to get your API key and follow the setup instructions.

Server Config

{
  "mcpServers": {
    "mockuuups": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mockuuups.studio/mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Mockuuups
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