- MONITOR
- TARGET
- TERMINATE
- HUMAN
Short answer
How can I stop Modal apps using my AI?
Your agent uses Modal's API to list running apps and terminate specific ones on command. This gives you a direct way to kill processes without leaving your chat interface. You'll see how the agent handles identification and shutdown below.
Control your executions.
Manage active workloads.
The agent handles the heavy lifting of finding and stopping processes.
MONITOR
Identify active apps
The agent scans your account to find everything currently running. You get a clear view of what's consuming resources.
TARGET
Inspect specific apps
The agent pulls details for a single execution to ensure it's the right one to kill. This prevents accidental shutdowns.
TERMINATE
Kill runaway processes
The agent sends a stop command to the specific app ID you've identified. This immediately halts resource consumption.
HUMAN
Manual oversight
You decide which apps are safe to stop. The agent waits for your confirmation before pulling the plug on an execution.
The workflow
What your AI does when <the thing arrives>.
The agent moves from discovery to termination in three logical steps.
Scan for activity
The agent looks through your Modal account to find all currently running applications.
list_appsVerify the target
Once you pick an app, the agent checks its specific configuration and status to confirm it's the right target.
get_appExecute shutdown
The agent sends the command to stop the specific app execution you identified.
stop_appConfirm status
The agent re-checks the app list to ensure the process actually stopped.
list_apps
Try it
Copy these to start.
Use these prompts to take control of your Modal environment.
Starting points
These are starting points. Replace the specific app names or IDs with your actual Modal details.
Modal Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_yQfuiuyaifaMlCchZoeV6rYy4ok4PpgYEfzlMmar/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — Modal capabilities are ready to use.
{
"mcpServers": {
"modal-serverless-ai-infrastructure-mcp": {
"url": "https://edge.vinkius.com/vk_preview_yQfuiuyaifaMlCchZoeV6rYy4ok4PpgYEfzlMmar/mcp"
}
}
}List all my currently running Modal apps.
Find the details for the app with ID app-12345.
Stop the Modal app named 'image-processor-prod'.
Check if the app 'data-cruncher' is still running after I told you to stop it.
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect Modal once, then ask.
One connection gives your agent full control over your Modal executions. Your credentials stay encrypted and secure.
Connect Modal to your AIFAQ
How this task behaves.
- 01
Can the AI create new Modal apps?
No. This MCP is specifically for managing and stopping existing executions.
- 02
Will the AI stop apps without my permission?
No. The agent identifies and proposes the stop action, but you maintain final control over which apps are terminated.
- 03
Can the AI see my source code?
No. The agent only interacts with the app execution data provided by the Modal API.
- 04
How does the AI know which app to stop?
The agent uses the list of active apps to find the specific ID or name you've requested.
- 05
Can the AI change the configuration of an app?
No. The available tools are limited to listing, getting details, and stopping apps.
More questions about Modal? The Connector page answers them. See everything the Modal Connector can do
Connect Modal to Claude, Cursor, ChatGPT & more
