MCP Service MCP Server

MCP Service MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. bgm.tv MCP Server.

What you get

A Model Context Protocol (MCP) server that provides programmatic access to the Bangumi TV API, enabling AI assistants like Claude to interact with comprehensive anime, manga, music, game, and real-world media data.

• 55 MCP Tools — Complete coverage of Bangumi API endpoints
• 3 Workflow Prompts — Pre-built multi-step workflows for common tasks
• 1 Resource — Full OpenAPI specification for API documentation
• Modular Architecture — Clean, maintainable codebase following MCP best practices
• Type-Safe — Full Python type hints and enum definitions
• Async Support — Non-blocking API calls using httpx

What the assistant can call

Once MCP Service is connected, these are the calls the assistant has available:

• get_daily_broadcast — Weekly broadcast schedule
• search_subjects — Full-text search with filters
• browse_subjects — Category-based browsing
• get_subject_details — Detailed subject information
• get_subject_image — Subject image URL
• get_subject_persons — Related creators/staff
• get_subject_characters — Related characters
• get_subject_relations — Related subjects
• get_episodes — Episode list
• get_episode_details — Episode information
• search_characters — Character search
• get_character_details — Character information

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need one environment variable: BANGUMI_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.10 or higher - uv package manager (recommended) or pip

Choosing this one

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Service's toolset — get_daily_broadcast, search_subjects, browse_subjects and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Ukenn2112; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Service.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp service mcp server does with a few real requests.