Make.com MCP Server

Created By
elitaua year ago
An MCP server implementation that integrates parts of the Make.com API
Overview

what is Make.com MCP Server?

Make.com MCP Server is an implementation that integrates parts of the Make.com API, allowing users to read and manage various resources such as scenario blueprints and user data.

how to use Make.com MCP Server?

To use the Make.com MCP Server, clone the repository from GitHub, set up your environment with the necessary API key, and run the server to interact with the Make.com API.

key features of Make.com MCP Server?

  • Reads scenario blueprints from Make.com.
  • Supports various API scopes for comprehensive data access.
  • Allows running and writing scenarios through the API.

use cases of Make.com MCP Server?

  1. Automating workflows by reading and executing scenarios.
  2. Integrating Make.com resources into custom applications.
  3. Managing user data and scenario configurations programmatically.

FAQ from Make.com MCP Server?

  • What API scopes are supported?

The server supports multiple scopes including agents:read, apps:read, and scenarios:run.

  • How do I set up the server?

Clone the repository, install dependencies, and configure your API key in the setup file.

  • Can I use this server for production?

Yes, once properly configured, it can be used in production environments.

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