MCPs that run tasks without manual intervention
Automation MCP servers give AI agents the power to trigger workflows, orchestrate multi-step tasks, and react to events across your stack. They replace manual hand-offs between tools with a single agent conversation. Combined with scheduling, webhooks, and database MCPs, they form the backbone of any agentic automation.
Automation MCPs eliminate repetitive work by letting AI agents trigger workflows, schedule jobs, react to events, and chain actions across systems. Instead of manually copy-pasting between tools, your agent handles the plumbing end-to-end.
Every push to main triggers a Supabase migration automatically. Schema diffs are committed and applied with zero manual steps.
Open a PR and a Vercel preview URL appears as a comment within minutes. Branches are cleaned up automatically when PRs close.
A Linear issue assigned to a developer automatically creates a git branch, syncs status changes, and opens a draft PR.
Receive a Slack message for every successful payment, failed charge, and subscription cancellation in real time.
Any MCP server that exposes tools to trigger actions, orchestrate workflows, or chain events counts as automation. GitHub, Zapier, n8n, Make, and workflow engines all fall under this tag.
Yes — scheduling MCPs (cron) are the natural trigger source. Pair a cron MCP with GitHub + Slack to run a daily automation that posts deploy summaries at 9am.
They integrate with them. The MCP protocol lets Claude Code call Zapier/n8n as one of many agents, so you keep your existing flows while gaining natural-language triggering.
Use the MCPizy CLI: `mcpizy install github n8n slack stripe`. All servers configure themselves and populate your `.claude.json` in one step.
Browse the full marketplace or explore all tags to find the right MCPs for your stack.