p2p-tools-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| P2P_TOOLS_CONFIG | No | Path to a YAML configuration file. When unset, the servers use loopback defaults for Jackett and qBittorrent, but authenticated operations will still require their credentials. |
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 |
|---|---|
| vpn_statusA | Return NordVPN connection status |
| vpn_connectC | Connect NordVPN. Optional argument: country. |
| vpn_disconnectA | Disconnect NordVPN |
| vpn_public_ipA | Return current public IP address |
| vpn_require_activeA | Fail unless NordVPN is connected |
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 5 tools
Each tool has a clearly distinct purpose: connect, disconnect, check status, get public IP, and enforce an active connection. No two tools overlap in functionality, reducing the chance of misselection.
All tools share the vpn_ prefix and use snake_case, which is consistent. There is a slight mix of verb-based names (vpn_connect, vpn_disconnect, vpn_require_active) and noun-based names (vpn_status, vpn_public_ip), but the pattern remains predictable and readable.
Five tools is a well-scoped set for a VPN control server, covering the essential operations without unnecessary redundancy. The count is appropriate for the domain and neither sparse nor bloated.
The tool set covers the core VPN lifecycle: connect, disconnect, status, public IP, and an active-connection guard. Minor gaps exist, such as listing available countries or retrieving current server details, but these are not critical for basic workflows and can be worked around.