Tag12 MCPs tagged here

Automation

MCPs that run tasks without manual intervention

TL;DR

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.

About 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.

Common use cases

  • Trigger deployments automatically on git push
  • Auto-create tickets from error reports or customer emails
  • Chain Stripe payments → Notion invoicing → Slack notification
  • Orchestrate multi-step onboarding workflows for new users
  • Run end-of-day reports across multiple data sources

Frequently asked questions

What makes an MCP an 'automation' MCP?

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.

Can I combine automation MCPs with scheduling?

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.

Do these replace Zapier or n8n?

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.

How do I install multiple automation MCPs at once?

Use the MCPizy CLI: `mcpizy install github n8n slack stripe`. All servers configure themselves and populate your `.claude.json` in one step.

Install Automation MCPs

Browse the full directory or explore all tags to find the right MCPs for your stack.