IFTTT MCP server

com.iftttPublished by ifttt.comOfficial publisherv1.0.0Updated Oct 24, 2026

Automate 1,000+ services from any MCP-compatible AI agent: build Applets, run actions and queries.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

IFTTT's hosted MCP server lets an AI assistant discover IFTTT services, build Applets, and run actions and queries across 1,000+ connected services.

What you can do
  • Discover IFTTT services and what they can trigger or act on
  • Build and manage Applets that connect triggers to actions
  • Run direct actions and queries against connected services
  • Work across hundreds of integrations such as Gmail, Google Sheets, Philips Hue and Webhooks
When to use it
Useful when you want an assistant to automate everyday tasks across third-party services through IFTTT, for example creating an Applet or firing an action in a connected service, rather than working inside one app.
Requirements
A remote MCP endpoint at ifttt.com/mcp with OAuth sign-in; the first use opens IFTTT's browser sign-in page, and a free IFTTT account is enough. No packages, environment variables or headers are declared.
Before you install
OAuth access to your IFTTT account is granted to the client. Actions and Applets it creates run against real connected services and can send, change or delete data there, so review what the assistant is about to do. The hosted server is closed source.

Installation

In SourceWeft

  1. Open IFTTT MCP server in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.ifttt%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ifttt": {
      "type": "http",
      "url": "https://ifttt.com/mcp"
    }
  }
}

README

IFTTT Plugins

IFTTT is "if this, then that" — automation across hundreds of services, from Gmail and Google Sheets to Philips Hue and Webhooks. This repository packages that power for AI clients: official plugins that connect an agent to IFTTT's hosted MCP server at https://ifttt.com/mcp and teach it to discover services, build Applets, and run actions responsibly.

The MCP server itself is hosted by IFTTT and closed source. This repo holds only what runs inside your client: manifests, skills, rules, and assets.

Plugins

PluginDescription
iftttService discovery, Applet building and management, and direct actions and queries

Installing

Cursor is our launch client — open cursor.com/marketplace/ifttt and click Install.

Running OpenClaw? Install the skill from ClawHub:

sh
openclaw skills install @ifttt/ifttt

Not on either? Any MCP-compatible client can point at the server directly:

json
{  "mcpServers": {    "ifttt": {      "type": "http",      "url": "https://ifttt.com/mcp"    }  }}

The first time the server is used, your browser opens IFTTT's sign-in page. A free account is enough — approve access and you're set.

Repository layout

.cursor-plugin/marketplace.json  Cursor marketplace manifest — lists every plugin under plugins/plugins/<name>/  .cursor-plugin/plugin.json     Cursor plugin manifest  mcp.json                       server connection (Cursor's default MCP config name)  skills/                        workflows the agent can load (SKILL.md each)  rules/                         always-on guardrails (.mdc)  assets/                        logo and icon  README.md                      user-facing docsopenclaw/<name>/  SKILL.md                       ClawHub-format skill for OpenClaw agentsserver.json                      entry for the official MCP Registryllms.txt                         discovery index for LLM crawlersscripts/validate.mjs             structure checks (run in CI)

Cursor reads the root marketplace manifest first and ingests only the plugins it lists, so a new plugin needs an entry there as well as its own directory.

Contributing

Run node scripts/validate.mjs before opening a PR — CI runs the same checks. CONTRIBUTING.md covers scope, conventions, and local testing; AI agents working in this repo should start with AGENTS.md.

Links

Source: README.md at commit 311ec27

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts