IFTTT

Run IFTTT actions, query services and create Applets.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the IFTTT connector does

The IFTTT MCP server connects an IFTTT account — the automation platform whose Applets wire one service's trigger to another's action — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 14 tools and IFTTT documents 20. Two of them dispatch into IFTTT's whole catalogue, so no tool count describes what this connector reaches.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

IFTTT tools (14)

  • get_user_info
  • get_services
  • search_services
  • get_triggers
  • get_actions
  • get_queries
  • run_action
  • run_query
  • search_applets
  • get_applet
  • create_applet
  • enable_applet
  • connect_service
  • geocode

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Anthropic's directory under-lists this server by six tools. The missing names are get_steps, my_applets, edit_applet, disable_applet, remove_applet and set_applet_filter_code. Audit against IFTTT's plugin repository, not the directory listing.
  • The tool count does not bound the capability. Two of the tools dispatch by identifier into IFTTT's catalogue. Treat 20 as the size of the interface and 4,142 as the size of the surface.
  • One OAuth scope, and it draws no line. IFTTT's resource descriptor, its authorization server metadata and its 401 challenge all name a single scope, mcp. Nothing at the grant separates reading from acting, and no boundary falls between a routine write and an irreversible one.
  • The only real permission boundary is your connected-service list. It lives in your IFTTT account, not in the MCP grant, and no configuration change is required to widen it — connect_service is itself one of the tools.
  • IFTTT's safety guidance is not enforced. The ifttt-lifecycle rules that require confirmation before remove_applet and run_action ship as client-side plugin files. A client that has not installed them never receives them.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or readOnlyHint value is published here.
  • The documentation URL IFTTT's own OAuth metadata nominates is dead. Both the RFC 9728 descriptor's resource_documentation field and the authorization server's service_documentation field point at https://ifttt.com/docs/mcp, which returned 404 on 2026-08-22. The working page is https://ifttt.com/mcp.
  • No MCP-level rate limit is documented. IFTTT publishes per-service limits — 100 tweet actions a day, 100 phone calls a month, 30 emails a day on Free against 750 on Pro — and states that "The majority of services on IFTTT do not have any rate limits applied by IFTTT". Nothing limits tool calls as such.
  • Applet counts are plan-gated. IFTTT's plans page caps Free at 2 Applets and Pro at 20, so create_applet fails once the cap is reached.
  • Trigger latency differs by plan. IFTTT's service pages state that polling trigger checks run every 5 minutes for Pro and Pro-plus users and every hour for Free users, so an Applet enabled through the connector may not fire for an hour on a free account.
  • Editing a community Applet silently forks it. IFTTT's guardrails state that a response carrying made_it_your_own set to true means a new user-owned copy was created. An agent that believes it edited a shared Applet may have created a second one.
  • The privacy policy the directory links does not mention this connector. https://ifttt.com/terms is IFTTT's general terms and privacy policy, dated April 2026. It contains no clause about AI assistants, MCP or agent access.
  • Whether IFTTT logs MCP-initiated actions distinctly is unresolved. We found no documentation stating whether an action run through the connector is distinguishable in IFTTT's activity log from one run by an Applet. Treat it as unknown.

Frequently asked questions

How many tools does the IFTTT MCP server have?

Twenty, not the fourteen Anthropic lists. IFTTT's own plugin repository documents twenty tool names under a Tool overview heading. The fourteen in Anthropic's directory are an exact subset, so nothing in the directory is fabricated — it is simply missing six, including remove_applet, which IFTTT's own guardrails describe as permanent.

How many operations can the IFTTT MCP server actually reach?

Far more than its tool count. Two tools take an action or query identifier as an argument and forward it into IFTTT's catalogue. IFTTT's services sitemap enumerated 2,722 actions and 1,420 queries across 1,053 services on 2026-08-22, so the reachable surface is 4,142 operations sitting behind two names.

Can the IFTTT connector unlock my front door or disarm my alarm?

Yes, if you have connected a lock or alarm service and hold an IFTTT Pro plan. IFTTT's services sitemap publishes 13 action slugs containing unlock and 24 containing disarm, including unlock_smartthings. Those are ordinary actions, reachable through the same run_action tool that turns on a light.

Does approving an IFTTT tool call tell me what will happen?

No. The approval prompt shows the MCP call, not its consequence, because the consequence is whatever your configuration and the third-party service do next. IFTTT concedes the point in its own guardrails, which instruct agents to confirm before run_action because messages get sent and devices get switched.

Is IFTTT MCP the same thing as Zapier MCP?

Same dispatcher shape, different disclosure. Both front a large write surface behind a few tool names. Zapier's directory entry lists zero tools because its set is built per user; IFTTT's is fixed and published. IFTTT is also countable — its sitemap enumerates every action — where Zapier's reachable actions cannot be diffed from outside.

What OAuth permissions does the IFTTT MCP server request?

One, and it draws no line. IFTTT's RFC 9728 resource descriptor and its authorization server metadata both declared scopes_supported as the single value mcp on 2026-08-22, and the 401 challenge repeats it. No scope separates listing your services from unlocking a door, because the grant has one setting.

Can an AI agent post publicly through IFTTT?

Yes, on a Pro plan. IFTTT's services sitemap publishes actions including post_new_tweet on X, status and photo actions on Facebook Pages, and a Flickr action uploading a public photo from a URL. Each is reachable through run_action once that service is connected. IFTTT caps tweet actions at 100 per day.

What does the IFTTT MCP server cost to use?

Nothing beyond your IFTTT plan, but the plan gates the risky half. IFTTT states Free users can search services and enable free Applets, Pro users additionally get the ability to run actions, and Pro-plus users unlock running queries. Free caps you at 2 Applets, Pro at 20, Pro-plus at unlimited.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put IFTTT to work.

Connect IFTTT once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.