IFTTT MCP server
by IFTTT
Actions across the services connected to your IFTTT account.
What it can do
- Run actions in connected services
- Read from connected services
- Trigger applets
Through MCP1, every tool call is checked against your groups and rules, and recorded in the audit log.
How it connects
Authenticate with IFTTT and approve MCP1. No token to copy; MCP1 keeps the connection sealed and refreshes it.
Connect the services you want to use in IFTTT first.
- Endpoint
https://ifttt.com/mcp- Transport
- Streamable HTTP
- Docs
- ifttt.com
With MCP1
IFTTT for the whole team, behind one URL
- 01
Install it once
An admin adds IFTTT from the MCP1 catalog. Its authentication or token stays sealed in MCP1, never on a laptop.
- 02
Decide who gets what
Open it to groups, fully or read-only, and set rules per tool. Destructive tools can need an admin.
- 03
Connect any client
Claude, Cursor, ChatGPT, Codex and the rest connect one gateway URL and sign in with their own account.
More for operations & productivity
See all operations & productivity servers- PagerDutyEngineering
Incidents, services, schedules and who is on call.
Token - ChecklyEngineering
Synthetic checks, monitors, alerts and test results on Checkly.
Token - incident.ioEngineering
Incidents, alerts, on-call schedules and follow-ups.
One-click auth - RootlyEngineering
Incidents, alerts, on-call shifts and past resolutions on Rootly.
One-click auth - Better StackEngineering
Uptime monitors, incidents, on-call, logs and status pages.
One-click auth - PortEngineering
Query your Port catalog, scorecards and run self-service actions.
One-click auth
