mcp-registry/io.github.trycourier/courier/invoke_ad_hoc_automation / alternatives

Live alternatives to mcp-registry/io.github.trycourier/courier/invoke_ad_hoc_automation

The best live alternatives to mcp-registry/io.github.trycourier/courier/invoke_ad_hoc_automation right now are mcp-registry/com.b2bware/mcp-server/list_available_automation_actions, mcp-registry/io.github.foundrynet/forge-mcp/disable_automation, mcp-registry/com.b2bware/mcp-server/create_automation_flow, mcp-registry/io.github.foundrynet/forge-mcp/activate_automation, mcp-registry/io.github.shree-git/sendit/create_workflow — capability-matched and ranked by current reliability. mcp-registry/io.github.trycourier/courier/invoke_ad_hoc_automation itself is currently "healthy".

alternative	server
mcp-registry/com.b2bware/mcp-server/list_available_automation_actions	com.b2bware/mcp-server	live status →
mcp-registry/io.github.foundrynet/forge-mcp/disable_automation	io.github.FoundryNet/forge-mcp	live status →
mcp-registry/com.b2bware/mcp-server/create_automation_flow	com.b2bware/mcp-server	live status →
mcp-registry/io.github.foundrynet/forge-mcp/activate_automation	io.github.FoundryNet/forge-mcp	live status →
mcp-registry/io.github.shree-git/sendit/create_workflow	io.github.Shree-git/sendit	live status →
mcp-registry/io.github.loved0543-dotcom/no-shell-agent-architect-mcp/design_automation_stack	io.github.loved0543-dotcom/no-shell-agent-architect-mcp	live status →
mcp-registry/io.github.foundrynet/forge-mcp/create_automation	io.github.FoundryNet/forge-mcp	live status →
pulsemcp/100hires/hires_create_nurture_campaign	100Hires	live status →
mcp-registry/com.100hires/100hires/hires_create_nurture_campaign	com.100hires/100hires	live status →
mcp-registry/com.quintadb/mcp/run_action	com.quintadb/mcp	live status →
mcp-registry/ua.com.quintadb/mcp/run_action	ua.com.quintadb/mcp	live status →
mcp-registry/ru.quintadb/mcp/run_action	ru.quintadb/mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.trycourier/courier/invoke_ad_hoc_automation?

mcp-registry/com.b2bware/mcp-server/list_available_automation_actions is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.foundrynet/forge-mcp/disable_automation, mcp-registry/com.b2bware/mcp-server/create_automation_flow, mcp-registry/io.github.foundrynet/forge-mcp/activate_automation, mcp-registry/io.github.shree-git/sendit/create_workflow. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.trycourier/courier/invoke_ad_hoc_automation down right now?

mcp-registry/io.github.trycourier/courier/invoke_ad_hoc_automation's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.trycourier%2Fcourier%2Finvoke_ad_hoc_automation.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.trycourier%2Fcourier%2Finvoke_ad_hoc_automation or MCP find_alternatives. Check mcp-registry/io.github.trycourier/courier/invoke_ad_hoc_automation's live status: https://glimind.com/tool/mcp-registry/io.github.trycourier/courier/invoke_ad_hoc_automation.