Can I use Modal as a CLI?

Yes. KosmoKrator exposes a Modal CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Modal through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Modal tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Modal credentials stored?

Modal credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Modal MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Modal MCP Integration for Claude Agent SDK

Connect Modal to Claude Agent SDK through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write API key auth

Submit Modal feedback View package source

Connect Modal to Claude Agent SDK

Give Claude Agent SDK workflows access to KosmoKrator integrations through a local MCP server.

Add a KosmoKrator stdio MCP server to the Claude Agent SDK options. The gateway is local, scoped to this integration, and starts with --write=deny so Claude Agent SDK can inspect read-capable tools without receiving write access by default.

Modal MCP Config for Claude Agent SDK

Use a narrow integration list so the agent does not load unrelated tools.

{
  "mcpServers": {
    "kosmokrator-modal": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=modal",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=modal --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Modal instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Modal Tools Visible to Claude Agent SDK

Claude Agent SDK sees stable MCP tool names generated from the Modal integration catalog.

MCP tool	Source function	Type	Description
`integration__modal__modal_list_apps`	`modal.modal_list_apps`	Read	List all Modal apps. Returns app IDs, names, and status details.
`integration__modal__modal_get_app`	`modal.modal_get_app`	Read	Get details for a specific Modal app by ID, including status and metadata.
`integration__modal__modal_list_functions`	`modal.modal_list_functions`	Read	List all functions for a Modal app. Returns function IDs, names, and runtime details.
`integration__modal__modal_list_schedules`	`modal.modal_list_schedules`	Read	List all scheduled functions for a Modal app. Returns schedule IDs, cron expressions, and function details.
`integration__modal__modal_list_volumes`	`modal.modal_list_volumes`	Read	List all Modal volumes. Returns volume IDs, names, and size details.
`integration__modal__modal_list_secrets`	`modal.modal_list_secrets`	Read	List all Modal secrets. Returns secret names and creation dates (values are not exposed).
`integration__modal__modal_get_current_user`	`modal.modal_get_current_user`	Read	Get the current authenticated Modal user information, including name, email, and account details.

Related Modal Pages

Modal CLIUse direct JSON commands instead of MCP discovery. Modal MCPFull gateway reference and MCP tool names. KosmoKrator for Claude Agent SDKClient-level gateway setup.