Skip to main content
Glama
runapi-ai

@runapi.ai/gemini-omni-mcp

by runapi-ai

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RUNAPI_API_KEYYesYour RunAPI API key

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
{
  "listChanged": true
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
loginA

Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json.

text_to_video

Create a Gemini Omni task on RunAPI (text to video). Returns a task id, status, and output URLs.

create_audioB

Run a synchronous Gemini Omni operation on RunAPI (create audio). Returns the operation result.

create_character

Run a synchronous Gemini Omni operation on RunAPI (create character). Returns the operation result.

get_taskA

Fetch the current status and latest result payload for a gemini-omni task.

check_pricing

Look up RunAPI pricing for the gemini-omni model line.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct operation: authentication, video generation, audio generation, character creation, task retrieval, and pricing. The similar descriptions for create_audio and create_character are clarified by their names, leaving no real ambiguity.

Naming Consistency3/5

Most tools follow a verb_noun pattern (create_audio, create_character, get_task, check_pricing), but 'login' is a bare verb and 'text_to_video' is an action-object phrase without a leading verb. This mix is readable but not fully consistent.

Tool Count5/5

Six tools is a well-scoped set for a Gemini Omni integration, covering authentication, content generation, task status, and pricing. Each tool has a clear purpose and the count is appropriate for the server's domain.

Completeness4/5

The server covers core generation types (video, audio, character) and task status, but lacks operations like listing or canceling tasks. The missing lifecycle operations are minor and workable for most workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues