# IFTTT (MCP archived)

> Fire IFTTT applets via webhooks from an AI agent. Community MCP wrapper archived; IFTTT itself is unaffected.

[Canonical HTML page](https://top-mcps.com/mcp/ifttt) · [server.json](https://top-mcps.com/mcp/ifttt.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "ifttt": {
      "command": "npx",
      "args": [
        "-y",
        "ifttt-mcp"
      ],
      "env": {
        "IFTTT_WEBHOOK_KEY": "${IFTTT_WEBHOOK_KEY}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export IFTTT_WEBHOOK_KEY=your-maker-webhook-key
claude mcp add ifttt -- npx -y ifttt-mcp
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "ifttt": {
      "command": "npx",
      "args": [
        "-y",
        "ifttt-mcp"
      ],
      "env": {
        "IFTTT_WEBHOOK_KEY": "${IFTTT_WEBHOOK_KEY}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "ifttt": {
      "command": "npx",
      "args": [
        "-y",
        "ifttt-mcp"
      ],
      "env": {
        "IFTTT_WEBHOOK_KEY": "${IFTTT_WEBHOOK_KEY}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "ifttt": {
      "command": "npx",
      "args": [
        "-y",
        "ifttt-mcp"
      ],
      "env": {
        "IFTTT_WEBHOOK_KEY": "${IFTTT_WEBHOOK_KEY}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "ifttt": {
      "command": "npx",
      "args": [
        "-y",
        "ifttt-mcp"
      ],
      "env": {
        "IFTTT_WEBHOOK_KEY": "${IFTTT_WEBHOOK_KEY}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "ifttt-mcp"
          ],
          "env": {
            "IFTTT_WEBHOOK_KEY": "${IFTTT_WEBHOOK_KEY}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.ifttt]
command = "npx"
args = [
  "-y",
  "ifttt-mcp",
]
env = { IFTTT_WEBHOOK_KEY = "${IFTTT_WEBHOOK_KEY}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "ifttt": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "ifttt-mcp"
        ]
      },
      "env": {
        "IFTTT_WEBHOOK_KEY": "${IFTTT_WEBHOOK_KEY}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

IFTTT (MCP archived) doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

```none

```

## At a glance

- **Maintainer:** Community
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** IFTTT_WEBHOOK_KEY
- **Supported clients:** Claude, Cursor, VS Code, Any MCP-compatible client, IFTTT account with Webhooks service
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-31
- **Score:** 59/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/community-mcp/ifttt-mcp

## Security & scope

- **Access scope:** network
- **Sandbox:** IFTTT webhook key in env. The key is global to the account — anything that fires it can trigger any applet on that account.
- **Gotchas:**
  - One key per account, no per-applet scoping — leakage means full applet access.
  - Webhooks are write-only; you cannot audit from the MCP side. IFTTT activity log is the trail.
  - Smart-home applets that unlock doors or fire alarms are exactly as dangerous as they sound. Confirmation gates in your client.

## Quick answer

**What it does.** Sends webhook events to IFTTT applets via the Maker Webhooks service.

**Best for:**
- Fire-and-forget smart-home triggers
- Consumer-grade integrations
- Lightweight notification flows
- Long-tail IFTTT-only integrations

**Not for:**
- Run inspection / debugging (no read API)
- Complex multi-step workflows
- Business-critical automation

## Description

A lightweight MCP that wraps the IFTTT Webhooks service so an AI agent can trigger any applet that listens on a webhook event. The simplest of the automation MCPs — one tool, one credential, one URL pattern — and pairs well with the long tail of consumer-grade integrations IFTTT supports that the bigger platforms do not. Note: the community ifttt-mcp package is archived — no upstream maintenance. IFTTT itself is current; new installs that need only the webhook trigger can call the Maker Webhooks URL directly via a generic Fetch MCP.

## Why it matters

IFTTT covers consumer-grade integrations (smart home, Twitter/X, RSS, Apple/Google Photos) that pro automation tools either ignore or charge for. A trivial MCP wrapper unlocks all of it for agent workflows.

## Key features

- IFTTT Webhooks (Maker) auth
- Up to 3 string values per event
- Single-tool surface
- No external dependencies

## FAQ

### How does it authenticate?

Single Webhooks (Maker) key per IFTTT account. Find it under ifttt.com/maker_webhooks. Any agent with the key can fire any applet listening on that key.

### Can it read state?

No — IFTTT Webhooks are write-only. For two-way integrations use a richer platform.

### Rate limits?

IFTTT throttles per account; expect to be fine for personal use, gated on the IFTTT Pro plan for higher volume.

### Why use it over Zapier?

Cheaper and simpler for the consumer-grade integrations IFTTT specializes in. Zapier wins for business SaaS; IFTTT wins for smart-home, RSS, and social.

## Changelog

- **2026-05-31** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-04-05** — Initial directory listing.