"Make" matching MCP servers:

A Model Context Protocol server that enables LLMs to safely execute make targets from a Makefile, allowing AI assistants to run tests, format code, and automate various development tasks through natural language interaction.

Audits Make.com scenario blueprints before import, checking for hardcoded secrets, dangling references, plain-HTTP URLs, and other issues. Provides tools to inspect blueprint structure, trace module mappings, and generate a safety findings report.

Connects Claude to Make.com to manage scenarios: list, run, activate/deactivate, and monitor executions.

Local-first visual design workspace for AI assistants. Compose wireframes and branded multi-page HTML/CSS documents with live preview, annotations, brand and asset libraries, typed data collections, layout validation, PDF export, and draft-only Gmail handoff.

MCP server for AI Diagram Maker — generate software engineering diagrams from natural language, code, ASCII diagram, images, or Mermaid. Inline diagram rendering using MCP apps UI and diagram URL in responses. Works with Cursor, Claude Desktop, Claude Code, and any MCP-compatible AI.

Create free, no-signup invoices from your AI assistant — the create_invoice tool returns a link that opens blankinvoicemaker.com pre-filled, ready to download as a watermark-free PDF.

Generate styled QR codes, manage dynamic short links with click analytics, and publish micro-landing pages via AI agents.

Enables AI-assisted GameMaker project development in Cursor IDE, allowing users to create projects, add scripts, objects, and sprites using natural language.

Provides read-only access to Make Bracket Online bracket maker features including editor workflows, official links, and FAQ for AI assistants.

Exposes the Tier Maker List browser editing workflows, local processing boundaries, FAQ, and official links to MCP-compatible AI clients like Claude Desktop and Cursor. Read-only, no API keys, ~50 ms cold start.

Enables creating RPG Maker MZ games using natural language through AI assistance, with tools for project management, map creation, event systems, and batch operations.

Enables AI assistants to act as co-developers for RPG Maker MV projects, providing full database CRUD, map and event editing, plugin management, playtest control, and automatic backups.

Enables AI agents to directly manipulate RPG Maker MZ projects through natural language commands, allowing creation and modification of game assets like items, weapons, enemies, maps, and plugins without manually editing game files.

Enables AI models to develop and automate RPG Maker MZ projects by creating maps, events, and plugins through natural language commands. It provides comprehensive tools for database management, asset integrity checks, and direct map tile manipulation.

A Model Context Protocol server that enables management of RPG Maker MZ and MV project data, including actors, items, maps, and events. It allows users to create, update, and search game assets through natural language integration with MCP-compatible clients.

Enables Claude to make outbound phone calls through Vapi API, supporting any call type and language with features like call initiation, result polling, and structured data extraction.

Generate AI UGC videos for your app from any MCP client: create an AI influencer, make her photo, turn it into a talking 5 or 10 second video, add your app screen recording and a hook line, download the file. Needs a ClipUGC API key.

Enables AI agents to make pay-as-you-go AI inference requests through x402 with automatic Solana USDC payments, no API keys or registration, while enforcing configurable spending limits.

A local MCP server that lets Claude Code read Ringg AI assistants, knowledge bases, and call history, and make targeted edits to prompts, custom variables, and knowledge base attachments without placing calls.

mcp-broker is a local Model Context Protocol process broker for MCP clients. Think PgBouncer for MCP: one stable local endpoint in front of many upstream MCP servers. The broker owns upstream startup, reuse, cleanup, profile exposure, status, and safe tool routing. The core idea is simple: do not make every agent session load every upstream tool definition before the user asks a task.