M-Team MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MTEAM_API_KEY | Yes | M-Team API authentication key (Required). You can obtain this from the M-Team website's personal settings. | |
| MTEAM_API_BASE | No | API base URL. | https://api.m-team.cc/api |
| MTEAM_DOWNLOAD_DIR | No | Directory to save downloaded torrent files. | ./seed |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_torrentsA | Search torrents on M-Team by keyword. Args: keyword: Search keyword (supports Chinese / English). mode: Search mode. One of: normal, adult, movie, music, tvshow, waterfall, rss, rankings, all. Defaults to "normal". page_number: Page number (1-based). Defaults to 1. page_size: Number of results per page (max 100). Defaults to 20. Returns: A formatted string listing matching torrents with their IDs, names, sizes, seeder/leecher counts, labels, ratings, and discount info. |
| get_torrent_detailA | Get detailed information for a specific torrent by its ID. Args: torrent_id: The numeric torrent ID (e.g. "1125330"). Returns: A formatted string with full torrent details including name, size, description, ratings, file count, seeder/leecher counts, etc. |
| download_torrentA | Download a .torrent file for the given torrent ID. This tool first obtains a temporary download token from the M-Team API, then downloads the .torrent file and saves it to the configured download directory (default: ./seed/). Args: torrent_id: The numeric torrent ID (e.g. "1125330"). Returns: The absolute path to the saved .torrent file on success, or an error message on failure. |
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 serves a unique purpose: search finds torrents, detail retrieves information, and download fetches the torrent file. No overlap or ambiguity exists.
All tool names follow a consistent verb_noun snake_case pattern (download_torrent, get_torrent_detail, search_torrents), making it predictable for agents.
With 3 tools, the set is small but covers essential torrent operations (search, detail, download). Slightly under for full lifecycle but reasonable for a basic client.
The tools cover searching, viewing details, and downloading torrents, but miss uploads, deletions, or seed management. Notable gaps exist for a complete torrent management server.