io.github.lasan713/alertforge

up checked 2026-11-11T02:38:07.083Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

AlertForge

Publisher-provided description

Create stream overlays, AI alerts, and transparent videos through AlertForge.

Summary by lookupd

Plans and generates stream overlays, AI alert graphics and transparent videos, then checks render status and exports the finished packs.

Install

Claude Code, remote (streamable-http)

claude mcp add --transport http alertforge https://alertforge.ai/api/mcp

Codex, remote (streamable-http)

codex mcp add alertforge --url https://alertforge.ai/api/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "alertforge": {
      "url": "https://alertforge.ai/api/mcp"
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (24 tools)

Publisher-provided text

• get_product_info Read-only. What AlertForge is, its key features, supported streaming platforms, and OBS-ecosystem compatibility.
• list_scene_kinds Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• list_particles Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• get_balance Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• list_overlay_projects Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• plan_design_sheet Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• create_design_sheet Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• approve_design_sheet Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• plan_style_sheet_character_edit Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• create_style_sheet_character_edit Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• get_style_sheet_character_edit_status Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• plan_overlay_pack Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• create_overlay_pack Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• get_pack_status Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• export_pack_zip Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• list_alert_types Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• plan_alert_pack Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• create_alert_pack Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• get_alert_pack_status Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• generate_alert_character Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• get_alert_character_status Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• plan_transparent_video Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• create_transparent_video Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and
• get_render_status Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and

Details

• Version: 1.0.0
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 442 ms
• First indexed: 2026-11-01T09:38:14.178Z
• Last seen in registry: 2026-11-01T09:38:14.178Z
• Repository: https://github.com/lasan713/alertforge-agent-plugin
• Website: https://alertforge.ai/ai-agents

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.github.lasan713/alertforge.svg)](https://lookupd.com/servers/io.github.lasan713/alertforge)

• 62071 servers
• Last crawl: 2026-11-11T16:17:25.167Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp