AITuber MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AITUBER_API_KEY | Yes | Your API key from AITuber dashboard | |
| AITUBER_API_BASE_URL | No | API base URL (override for self-hosted or testing) | https://app.aituber.app/api/v1 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_apiA | Search the AITuber API to find endpoints for creating AI videos, checking credits, exporting to MP4, publishing to YouTube/TikTok/Instagram, and more. Returns matching endpoints with parameters and examples. Use this before execute_api to find the right endpoint. |
| execute_apiA | Execute a request against the AITuber API. Use search_api first to find the right endpoint and parameters. Handles authentication automatically. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: search_api discovers endpoints and parameters, while execute_api performs the actual API call. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern (search_api, execute_api) using snake_case, making the naming predictable.
Two tools is minimal but suitable for the server's designed workflow of discovery followed by execution. While slightly thin, each tool serves a necessary and distinct role without redundancy.
The combination of search and execute covers the full lifecycle of using the AITuber API: finding the right endpoint and then executing it. Authentication and parameter handling are included, leaving no obvious gaps.