Hololive MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_talentsA | Returns a formatted list of every talent listed on the official hololive English site — all generations and branches, including alumni — with their English name, Japanese name, and profile URL slug. |
| get_talent_profileA | Fetches the profile page for a specific talent using their URL slug (e.g., 'mori-calliope', 'gawr-gura'). Returns their catchphrase, biography, and social links. |
| get_recent_newsA | Fetches the latest headlines from the hololive English news page (up to 10 items). Note that each entry includes the full article body, not just the title. |
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 3 tools
Each tool targets a distinct resource and action: enumerating all talents, fetching a single talent's profile by slug, and fetching news headlines. There is no plausible way to confuse these three operations, and the descriptions reinforce the boundaries (list returns names/slugs, profile requires a slug from that list).
All three tools follow a clean verb_noun snake_case pattern: list_talents, get_talent_profile, get_recent_news. The verb choice also meaningfully distinguishes collection-level (list) from item-level (get) retrieval.
Three tools is on the lean side but each earns its place and covers a genuinely different need (roster, profile detail, news). It is a tightly scoped read-only scraping server, so the small surface is defensible rather than anemic.
The talent lifecycle is well covered: list_talents returns every slug, and get_talent_profile resolves any of them, so there are no dead ends. Minor gaps exist around filtering/searching by generation or branch and around fetching older news beyond the latest 10 items, but agents can work around both.