Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MODAL_BINNoPath to `modal` CLI binarymodal
SUPABASE_KEYYesSupabase service role key
SUPABASE_URLYesSupabase project URL
MODAL_VOICE_CLONE_URLNoModal voice clone endpoint URL
MODAL_REMOTION_RENDER_URLNoModal render endpoint URL

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
modal_renderA

Render a Remotion composition on Modal cloud (Chrome + FFmpeg), upload to Supabase Storage, save job to memory. Returns public MP4 URL. Valid formats: instagram_ugc_v1, instagram_reel_v1, explainer_v1, listicle_v1, shorts_v1, devvlog_v1, tiktok_v1, twitter_v1, linkedin_v1, etc.

modal_render_listA

List recent Modal render jobs from Supabase memory. Shows status, URL, render time, and label.

modal_render_getA

Get a single Modal render job by job_id. Returns URL and full metadata.

modal_voice_cloneA

Synthesize speech using Modal F5-TTS voice clone (Isaiah voice by default). Returns audio URL or base64.

modal_appsA

List all deployed Modal apps with their status, task count, and creation date.

modal_logsC

Get recent logs from a Modal app.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct resource and action without overlap: app listing, log retrieval, video rendering creation, render job retrieval, render job listing, and voice synthesis. The boundaries between video rendering, voice cloning, and general Modal app management are clearly demarcated.

Naming Consistency3/5

Mixed verb placement conventions: modal_apps and modal_logs imply actions (list/get) without suffixes, while modal_render_get and modal_render_list use explicit action suffixes. The base modal_render tool (create operation) lacks a suffix unlike its complementary tools, creating inconsistency within the render workflow cluster.

Tool Count5/5

Six tools is well-scoped for the server's apparent purpose covering Modal app monitoring, video rendering lifecycle management, and voice synthesis. The count hits the sweet spot for functionality without overwhelming the agent with redundant options.

Completeness3/5

Notable gaps in lifecycle coverage: apps only supports listing (missing get single app, deploy, delete), render jobs lack cancel/delete operations, and voice synthesis has no associated read/list functionality. The surface supports creation and partial reading but misses update/delete operations for persistent resources.

Maintenance

ActivityMaintained
ResponsivenessNo issues