Make

Created By
yoavnirana year ago
Overview

what is Make?

Make is a Model Context Protocol (MCP) server that exposes Cloudinary Upload & Admin API methods as tools for AI assistants, allowing them to trigger and interact with your Cloudinary cloud.

how to use Make?

To use Make, you need to install it with NodeJS and configure it in the Claude Desktop app by adding specific settings to the claude_desktop_config.json file.

key features of Make?

  • Enables AI systems to make calls to the Cloudinary API on your behalf.
  • Facilitates uploading and management of assets in your Cloudinary cloud.
  • Allows for the integration of Cloudinary actions as callable tools for AI assistants.

use cases of Make?

  1. Automating image uploads to Cloudinary through AI commands.
  2. Managing Cloudinary assets using AI-driven interfaces.
  3. Enhancing AI assistants with the ability to interact with media assets stored in Cloudinary.

FAQ from Make?

  • What are the prerequisites for using Make?

You need NodeJS and a compatible MCP Client like Claude Desktop App, along with a Cloudinary API Key/Secret.

  • Is Make free to use?

Yes, Make is free to use, but you need a Cloudinary account to access its features.

  • What methods are supported by Make?

Not all methods and parameters are supported initially, but more will be added over time. You can request specific methods by opening an issue on the GitHub repository.

Server Config

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "cloudinary-mcp-server"
      ],
      "env": {
        "CLOUDINARY_CLOUD_NAME": "<cloud name>",
        "CLOUDINARY_API_KEY": "<api-key>",
        "CLOUDINARY_API_SECRET": "<api-secret>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yoavniran
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