Allows AI models to manage a TeamSpeak 3 server via ServerQuery, including tools for server info, channel management, client management, groups, permissions, messaging, moderation, tokens, and file operations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@teamspeak3-mcp list all online clients on my server"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Let AI models manage your TeamSpeak 3 server through the Model Context Protocol.
A Model Context Protocol (MCP) server that exposes TeamSpeak 3 ServerQuery operations as AI-callable tools. Connect Claude, Cursor, or any MCP-compatible client to manage your TeamSpeak server with natural language.
35 purpose-built tools covering server management, channels, clients, groups, permissions, moderation, and more
Lazy connection — connects to TeamSpeak only when the first tool is invoked
Exponential backoff retry — automatic reconnection with up to 3 attempts
Graceful shutdown — cleans up the ServerQuery session on process exit
Centralized error handling — every tool returns structured MCP error responses
Zero-config transport — runs over stdio, works out-of-the-box with any MCP client
Related MCP server: CS2 RCON MCP Server
Node.js >= 18
A TeamSpeak 3 server with ServerQuery access (port 10011 by default)
Add the following to your MCP client configuration. This works with most clients:
{
"mcpServers": {
"teamspeak": {
"command": "npx",
"args": ["teamspeak3-mcp"],
"env": {
"TEAMSPEAK_HOST": "your-server.com",
"TEAMSPEAK_PASSWORD": "your-password"
}
}
}
}No installation needed — npx downloads and runs the package automatically.
Add to your Claude Desktop config file (claude_desktop_config.json):
{
"mcpServers": {
"teamspeak": {
"command": "npx",
"args": ["teamspeak3-mcp"],
"env": {
"TEAMSPEAK_HOST": "your-server.com",
"TEAMSPEAK_PASSWORD": "your-password"
}
}
}
}Add to your Cursor MCP settings (.cursor/mcp.json):
{
"mcpServers": {
"teamspeak": {
"command": "npx",
"args": ["teamspeak3-mcp"],
"env": {
"TEAMSPEAK_HOST": "your-server.com",
"TEAMSPEAK_PASSWORD": "your-password"
}
}
}
}Configuration is resolved from CLI arguments first, then environment variables, with sensible defaults as fallback.
Parameter | CLI Flag | Env Variable | Default |
Host |
|
|
|
Query Port |
|
|
|
Username |
|
|
|
Password |
|
| (required) |
Virtual Server ID |
|
|
|
Enabled Tools |
|
| (all) |
Note:
TEAMSPEAK_PASSWORDrefers to the ServerQuery login password, not the TeamSpeak server connection password. You can find it in the server console output on first start, or create one via Tools → ServerQuery Login in the TeamSpeak client.
By default all 35 tools are registered. Use TEAMSPEAK_TOOLS (or --tools) with a comma-separated list of module names to load only what you need — useful for reducing the tool list exposed to the AI model:
{
"mcpServers": {
"teamspeak": {
"command": "npx",
"args": ["teamspeak3-mcp"],
"env": {
"TEAMSPEAK_HOST": "your-server.com",
"TEAMSPEAK_PASSWORD": "your-password",
"TEAMSPEAK_TOOLS": "server,channel,client"
}
}
}
}Available modules: server, channel, client, sgroup, cgroup, permission, messaging, moderation, token, file
server_*)Tool | Description |
| Get server details (scope: |
| List resources (resource: |
| Search for clients or channels by pattern |
| View recent virtual server or instance log entries |
| Run a diagnostic check on the current connection's permissions |
channel_*)Tool | Description |
| Create a new channel (permanent or temporary) |
| Delete a channel (with optional force flag) |
| Update channel properties (name, password, codec, talk power, etc.) |
| Get detailed channel information |
| Add, remove, or list permissions on a channel |
client_*)Tool | Description |
| Get detailed info: platform, version, country, IP, idle time, etc. |
| Move a client to another channel |
| Kick a client from the server or channel |
| Ban a client (timed or permanent) |
| Manage server group membership and individual permissions |
| List historical clients from the server database (includes offline clients) |
| Send a poke alert notification to a client |
sgroup_*)Tool | Description |
| Create a new server group |
| Delete a server group |
| Add, remove, or list permissions on a server group |
| List all clients assigned to a server group |
cgroup_*)Tool | Description |
| Create a new channel group |
| Add, remove, or list permissions on a channel group |
| Assign a client to a channel group in a specific channel |
perm_*)Tool | Description |
| List all available permission definitions (name, ID, description) |
| Find all assignments of a permission across the server |
| Get effective permission overview for a client in a channel |
msg_*)Tool | Description |
| Send a text message (mode: |
ban_* / complaint_*)Tool | Description |
| List all active ban rules |
| Create, delete, or clear ban rules by IP/name/UID |
| List complaints (optionally filtered by target client) |
token_*)Tool | Description |
| List all available privilege keys/tokens |
| Create a server group or channel group token |
file_*)Tool | Description |
| List files in a channel's file repository |
| Get detailed info about a specific file |
git clone https://github.com/fl0w1nd/teamspeak3-mcp.git
cd teamspeak3-mcp
pnpm install
pnpm build # Build the project
pnpm dev # Watch mode (auto-rebuild on changes)
pnpm inspect # Debug with MCP Inspector (web UI)The project includes a pre-configured script for the MCP Inspector, a web-based debugging tool:
pnpm inspectThis launches a local web UI where you can browse available tools, invoke them interactively, and inspect request/response payloads — useful for development and troubleshooting.
src/
├── index.ts # Entry point, stdio transport, graceful shutdown
├── config.ts # CLI + env configuration parsing
├── connection.ts # TeamSpeak connection with retry & lazy init
├── server.ts # MCP server setup & tool registration
├── utils/
│ └── tool-handler.ts # Error handling & response utilities
└── tools/
├── server.ts # Server info, resource listing, search, logs, diagnostics
├── channel.ts # Channel CRUD & permissions
├── client.ts # Client management, permissions & poke
├── server-group.ts # Server group CRUD, permissions & members
├── channel-group.ts # Channel group CRUD, permissions & assignment
├── permission.ts # Global permission queries & overview
├── messaging.ts # Channel & private messaging
├── moderation.ts # Bans & complaints
├── token.ts # Privilege token management
└── file.ts # Channel file browserList all active ban rules on the virtual server
Inputs: no named parameters.
Create, delete, or clear ban rules on the server
Inputs: action (required), ip, uid, name, +3 more.
Assign a client to a channel group in a specific channel
Inputs: group_id (required), channel_id (required), client_db_id (required).
Create a new channel group
Inputs: name (required), type.
Manage permissions for a channel group: add, remove, or list
Inputs: action (required), group_id (required), value, permission.
Create a new channel on the server
Inputs: name (required), parent_id, permanent.
Delete a channel from the server
Inputs: channel_id (required), force.
Get detailed information about a specific channel
Inputs: channel_id (required).
Manage permissions on a specific channel: add, remove, or list
Inputs: action (required), channel_id (required), value, permission.
Update channel properties. Talk power presets: 0=normal, 50=moderated, 999=silent
Inputs: channel_id (required), name, password, permanent, +4 more.
Ban a client from the server
Inputs: client_id (required), reason, duration.
List historical clients from the server database (includes offline clients). Supports pagination for large databases
Inputs: limit, start.
Get detailed information about a specific online client
Inputs: client_id (required).
Kick a client from the server or current channel
Inputs: client_id (required), reason, from_server.
Move a client to another channel
Inputs: client_id (required), channel_id (required).
Manage a client's server group membership and individual permissions
Inputs: action (required), client_id (required), skip, value, +3 more.
Send a poke (alert popup) to a client — more attention-grabbing than a private message
Inputs: message (required), client_id (required).
List complaints on the virtual server, optionally filtered by target client
Inputs: target_client_db_id.
Get detailed information about a specific file in a channel's file repository
Inputs: file_path (required), channel_id (required), channel_password.
List files in a channel's file repository
Inputs: channel_id (required), path, channel_password.
Send a text message to a channel or a private message to a client
Inputs: mode (required), message (required), target_id (required).
Find all assignments of a specific permission across server groups, channel groups, channels, and clients
Inputs: permission (required).
List available permission definitions. Use 'filter' to search by keyword (e.g. 'kick') or 'category' to narrow by domain. Returns only names by default; set verbose=true for descriptions
Inputs: filter, verbose, category.
Get the effective permission overview for a client in a specific channel. Shows all permissions and their sources
Inputs: channel_id (required), client_db_id (required).
Diagnose current ServerQuery connection permissions and provide troubleshooting info
Inputs: no named parameters.
Get TeamSpeak server information. Use scope 'overview' for general server details, 'connection' for network/bandwidth statistics
Inputs: scope.
List server resources: online clients, channels, server groups, or channel groups
Inputs: resource (required).
View recent entries from the virtual server log
Inputs: lines, reverse, begin_pos, instance_log.
Search for online clients by name/UID or channels by name pattern
Inputs: type (required), pattern (required), by_uid.
List all clients assigned to a server group
Inputs: group_id (required).
Create a new server group
Inputs: name (required), type.
Delete a server group. Use force=true to remove even if clients are assigned
Inputs: group_id (required), force.
Manage permissions for a server group: add, remove, or list
Inputs: action (required), group_id (required), skip, value, +2 more.
Create a new privilege key/token for server or channel group access
Inputs: group_id (required), token_type (required), channel_id, custom_set, +1 more.
List all privilege keys/tokens available on the server
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 35 tools
Most tools have clearly distinct purposes, but the perm_* family (perm_overview, perm_list, perm_find, channel_perm, client_perm, sgroup_perm, cgroup_perm) has overlapping 'manage permissions' functions that could confuse without careful reading. Similarly, ban_* tools (ban_list, ban_manage, client_ban) have some overlap. Descriptions help distinguish them, but boundaries aren't always crisp.
Tool names mostly use a consistent verb_noun or noun_verb pattern (e.g., channel_create, client_kick, sgroup_perm), but there are minor deviations like server_list (noun_verb) and sgroup_create (abbreviated noun). The abbreviations (sgroup, cgroup, perm) are consistent within categories, making the naming predictable overall.
With 35 tools, the count is heavy for a TeamSpeak server management MCP. While many are distinct operations, the number could overwhelm an agent, and some tools (e.g., perm_overview vs perm_list) might be consolidated. The scope is broad, but the count feels borderline excessive.
The tool set covers most CRUD operations for channels, clients, server groups, channel groups, permissions, bans, messages, files, tokens, and complaints. However, some gaps exist: no tools for banning by IP/range, no detailed server group info beyond permissions, and no file upload/download operations. These are minor but noticeable for a complete management surface.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for AI dialogue using various LLM models via AceDataCloud
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.