get_pack_status — AlertForge MCP Tool Read-only
get_pack_status
(get pack status) is one of 24 tools on the
AlertForge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_pack_status from your client
- Claude Code AlertForge get_pack_status run in your project directory
- Claude Desktop AlertForge get_pack_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AlertForge get_pack_status ~/.cursor/mcp.json
- VS Code AlertForge get_pack_status .vscode/mcp.json
- Zed AlertForge get_pack_status ~/.config/zed/settings.json
- Windsurf AlertForge get_pack_status ~/.codeium/windsurf/mcp_config.json
- Cline AlertForge get_pack_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AlertForge get_pack_status ~/.gemini/settings.json
- Grok AlertForge get_pack_status .mcp.json (in your project root)
- ChatGPT AlertForge get_pack_status Settings → Connectors → Advanced → Developer mode
- Claude.ai AlertForge get_pack_status Settings → Connectors → Add custom connector
- LangChain AlertForge get_pack_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http alertforge https://alertforge.ai/api/mcp
Other tools on this server
- get_product_info
- list_scene_kinds
- list_particles
- get_balance
- list_overlay_projects
- plan_design_sheet
- create_design_sheet
- approve_design_sheet
- plan_style_sheet_character_edit
- create_style_sheet_character_edit
- get_style_sheet_character_edit_status
- plan_overlay_pack
- create_overlay_pack
- export_pack_zip
- list_alert_types
- plan_alert_pack
- create_alert_pack
- get_alert_pack_status
- generate_alert_character
- get_alert_character_status
- plan_transparent_video
- create_transparent_video
- get_render_status
This list was read from the server itself, by connecting to it and calling tools/list on 27 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.