make_mcp CLAUDE.md

A set of Claude Code instructions for a fork of Make.com's MCP server. MCP, or Model Context Protocol, is a way for an AI assistant to call external tools; here, those tools interact with Make.com automations called scenarios.

In plain words
What is it for?
It helps install, build, test, inspect, and modify the server, including its ability to run and manage Make.com scenarios.
Why use it?
It gives the coding agent the project context, commands, architecture, and main request flow needed to work in this repository.

Instructions file

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/forayconsulting/make_mcp/claude-md
Clone the repo
git clone --depth 1 https://github.com/forayconsulting/make_mcp
Per session 1,102 This file is loaded in full into every session.
When invoked 1,102 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01102 $0.01102
Opus 5 $0.00551 $0.00551
Sonnet 5 $0.00220 $0.00220
Haiku 4.5 $0.00110 $0.00110

Measured 2d ago against content hash 4ac0db7cdb46, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

make_mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

This is a fork of the official Make.com MCP (Model Context Protocol) server. It exposes Make.com on-demand scenarios as callable tools for AI assistants. The goal of this fork is to extend capabilities beyond running scenarios to include full scenario lifecycle management (create, edit, delete).

Commands

npm install      # Install dependencies (also runs build via prepare script)
npm run build    # Compile TypeScript to build/
npm run watch    # Watch mode for development
npm test         # Run all tests
npm run inspector # Launch MCP Inspector for debugging

Run a single test:

npx jest test/server.spec.ts -t "Should get list of scenarios"

Architecture

Core Flow

index.ts (MCP Server)
    ↓
make.ts (Make API Client)
    ↓
Make.com REST API (https://{zone}/api/v2/...)

Source Files

  • src/index.ts - MCP server entry point. Registers two handlers:

    • ListToolsRequestSchema - Returns static management tools + dynamic run_scenario_{id} tools
    • CallToolRequestSchema - Dispatches to appropriate scenario method based on tool name
  • src/make.ts - Make API client with Scenarios class for API calls:

    • list(teamId) - Get all scenarios for a team
    • listOrganization(organizationId) - Get all scenarios for an organization
    • interface(scenarioId) - Get input/output schema for a scenario
    • run(scenarioId, body) - Execute scenario in responsive mode
    • get(scenarioId) - Get full scenario details
    • create(request) - Create a new scenario
    • update(scenarioId, request) - Update scenario metadata/blueprint
    • delete(scenarioId) - Delete a scenario (with confirmation)
    • clone(scenarioId, request) - Clone an existing scenario
    • activate(scenarioId) - Activate scenario via /start endpoint
    • deactivate(scenarioId) - Deactivate scenario via /stop endpoint
    • getBlueprint(scenarioId, options) - Get scenario blueprint
    • setInterface(scenarioId, request) - Set scenario input interface
    • getIncompleteExecutions(scenarioId) - Get DLQ entries

Read the full file on GitHub · 106 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 106 lines · 1,102 tokens per session scan A 4ac0db7cdb46

Subscribe to this mod's changes

make_mcp CLAUDE.md is an instructions file published in the GitHub repository forayconsulting/make_mcp (0 stars, last pushed 7mo ago), licensed MIT. It adds 1,102 tokens to every session, about $0.0055 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens