mteam-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MTEAM_API_KEY | Yes | M-Team API Key | |
| MTEAM_TIMEOUT | No | HTTP timeout in seconds | 30 |
| MTEAM_API_BASE | No | API root URL | https://api.m-team.cc/api |
| MTEAM_DOWNLOAD_DIR | No | Directory to save .torrent files | ~/.hermes/downloads/mteam |
| MTEAM_MAX_TORRENT_BYTES | No | Maximum torrent file size in bytes | 33554432 |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_torrentsA | Search M-Team torrents and return compact, AI-readable Markdown. Args:
keyword: Keyword, IMDb URL, or Douban URL. Empty text lists matching items.
mode: M-Team search mode, normally |
| get_torrent_detailC | Get one torrent's metadata as compact, AI-readable Markdown. |
| download_torrentA | Download a .torrent file after the user explicitly requests it. The temporary M-Team token remains internal. The result contains only the local saved path, torrent ID, and number of bytes written. |
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 has a clear, distinct purpose: searching for torrents, viewing torrent details, and downloading torrent files. There is no overlap or ambiguity.
All three tool names follow a consistent verb_noun pattern (search_torrents, get_torrent_detail, download_torrent) using snake_case, making it predictable and easy to understand.
With 3 tools, the set is minimal but covers the core functionality of a torrent client (search, detail, download). It is at the lower end of the typical range but still appropriate for a focused server.
The tools cover the essential workflow of searching, inspecting, and downloading torrents. Minor gaps like torrent removal or user-specific features are absent, but the core operations are fully covered.