Zapier
Register the LUU MCP server in Zapier's MCP Connections, then call LUU tools as a step inside any Zap. About 5 minutes from get-key to first running Zap.
What you'll get
Zapier's MCP integration (rolled out through 2025–2026) lets external LLMs invoke any of Zapier's 8,000+ connected apps as tools. In reverse, you can register the LUU MCP server in Zapier so that Zapier workflows (Zaps) can call LUU tools as steps. This is the most common pattern for non-technical buyers — it lets a Zap automatically forecast, fact-check, or generate briefs as part of an existing automation.
Prerequisites
- Zapier account (any tier with AI actions)
- An LUU API key — sign up (free tier: 25 calls/day, no card)
Pattern 1 — LUU MCP as a Zap step (recommended)
This pattern: a Zap is triggered (e.g. "new row in Google Sheets"), and the Zap calls LUU as one of its actions.
Step 1 — register the LUU MCP server
Go to Zapier → Settings → MCP Connections → Add MCP Server.
| Field | Value |
|---|---|
| Name | LUU |
| Type | HTTP |
| URL | https://api.leadershipunderuncertainty.org/api/mcp |
| Auth method | Bearer token |
| Token | your LUU API key |
Save.
Step 2 — use LUU in a Zap
In any Zap, add a step → AI by Zapier (or OpenAI / Claude — any LLM provider) → enable Use MCP tools → select LUU.
The LLM step now has access to all 27 LUU tools. In its prompt, write:
For each new row added to the Sheet:
1. Use luu_forecast to estimate the probability stated in column B.
2. Use luu_fact_check on the citation in column C.
3. Output a JSON object with { probability, citationVerified, rationale }.The LLM step calls LUU tools as needed and returns structured output. The next Zap step writes that output back to the Sheet.
Pattern 2 — Zapier as a downstream LUU consumer
This pattern: LUU emits an event (e.g. a new prediction crosses a threshold), and Zapier picks it up via webhook to trigger a downstream action.
LUU's webhook system supports this:
- See
/api/v1/webhooksand theluu_subscribetool for emitting events - In Zapier, create a Zap with Webhooks by Zapier → Catch Hook and use the URL it generates as the LUU webhook target
Typical use: "post a Slack message when our forecast probability for X moves more than 10pp."
Common Zap recipes
| Trigger | LUU step | Action |
|---|---|---|
| New row in Google Sheets | luu_forecast on the question | Write probability + rationale back to the row |
| New email tagged "intel" | luu_signals + luu_fact_check | Append to a Notion page |
| Daily 7 AM | luu_brief + luu_signals | Post to Slack channel |
| New CRM contact | get_strategic_landscape for actor map | Enrich CRM record |
| Inbound webhook from monitoring tool | luu_risk_assessment | Open a PagerDuty incident |
Troubleshooting
"MCP Connections" not visible in settings: Your account's plan or rollout cohort doesn't have it yet. Check Zapier's status page or contact support.
LUU tools don't appear in the AI step: Confirm the connection in MCP Connections shows status "Connected"; in the AI step, confirm "Use MCP tools" is enabled and the LUU server is selected.
Calls succeed but return empty: Your prompt may not be explicit enough. LLMs in workflow tools tend to call tools more conservatively than in chat. Add: "You MUST call luu_forecast for each input. Do not respond without making the call."
Cost notes
- Zapier's AI step pricing applies to the LLM (OpenAI/Claude) calls
- LUU's per-call rate limits + free-tier cap apply to the MCP tool calls
- Combined: an automation that runs 1,000 rows/day with 3 LUU calls each = 3,000 LUU calls/day. Plan key tier accordingly.
Next steps
- Try the n8n install guide for a self-hostable alternative with deeper AI integration
- See Claude Code workflow-integration template for a pre-built Zapier blueprint
- See SCO §6 Exchange Profiles to understand what each tool emits