MWS TeamStream MCP server
TeamStream MCP
MWS TeamStream's official MCP: an agent finds recordings by meaning and reads transcripts and summaries right from AI tools
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- The key grants access to the company's internal meeting recordings and workspaces
- The server only reads the video library, it does not publish or delete recordings
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/teamstream-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run in a terminal
claude mcp add --transport http teamstream https://mcp.teamstream.mws.ru/ --header 'Authorization: Bearer <your AUTHORIZATION>'Or add to the file .mcp.json, in the project
{
"mcpServers": {
"teamstream": {
"type": "http",
"url": "https://mcp.teamstream.mws.ru/",
"headers": {
"Authorization": "Bearer <your AUTHORIZATION>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
AUTHORIZATIONsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"teamstream": {
"url": "https://mcp.teamstream.mws.ru/",
"headers": {
"Authorization": "Bearer <your AUTHORIZATION>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
AUTHORIZATIONsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Run in a terminal
code --add-mcp '{"name":"teamstream","type":"http","url":"https://mcp.teamstream.mws.ru/","headers":{"Authorization":"Bearer <your AUTHORIZATION>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"teamstream": {
"type": "http",
"url": "https://mcp.teamstream.mws.ru/",
"headers": {
"Authorization": "Bearer <your AUTHORIZATION>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
AUTHORIZATIONsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.codex/config.toml, for all projects
[mcp_servers.teamstream]
url = "https://mcp.teamstream.mws.ru/"
http_headers = { Authorization = "Bearer <your AUTHORIZATION>" }If the file already exists, append the block to the end.
Keys and settings
AUTHORIZATIONsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"teamstream": {
"httpUrl": "https://mcp.teamstream.mws.ru/",
"headers": {
"Authorization": "Bearer <your AUTHORIZATION>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
AUTHORIZATIONsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"teamstream": {
"serverUrl": "https://mcp.teamstream.mws.ru/",
"headers": {
"Authorization": "Bearer <your AUTHORIZATION>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
AUTHORIZATIONsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"teamstream": {
"type": "streamableHttp",
"url": "https://mcp.teamstream.mws.ru/",
"headers": {
"Authorization": "Bearer <your AUTHORIZATION>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
AUTHORIZATIONsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"teamstream": {
"type": "streamable-http",
"url": "https://mcp.teamstream.mws.ru/",
"headers": {
"Authorization": "Bearer <your AUTHORIZATION>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
AUTHORIZATIONsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"teamstream": {
"type": "remote",
"url": "https://mcp.teamstream.mws.ru/",
"headers": {
"Authorization": "Bearer <your AUTHORIZATION>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
AUTHORIZATIONsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"teamstream": {
"url": "https://mcp.teamstream.mws.ru/",
"headers": {
"Authorization": "Bearer <your AUTHORIZATION>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
AUTHORIZATIONsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Create an MCP key in MWS TeamStream settings, connect the server at https://mcp.teamstream.mws.ru/ with an Authorization: Bearer <key> header, and for Claude Desktop use the mcp-remote wrapper to pass the same header.
Other ways from the author
{
"mcpServers": {
"teamstream": {
"url": "https://mcp.teamstream.mws.ru/",
"headers": {
"Authorization": "Bearer ВАШ_MCP_API_КЛЮЧ"
}
}
}
}Direct connection for clients that support a remote HTTP MCP with custom headers.
This is third-party code. Review the repository files before installing.
What it does
The server gives AI assistants direct access to the MWS TeamStream video library and workspaces. An agent can find recordings by natural-language description, get transcripts and summaries, read metadata such as author, date and duration, and check view analytics. In effect the video library becomes a knowledge base you can query straight from an IDE or an agent chat, without watching the recordings by hand.
Who it is for. For teams that record meetings and training videos in MWS TeamStream and want to find the moments they need through an agent instead of rewatching recordings.
Good fit when
- You need to find a specific recording or moment in it by meaning rather than by title
- You need a short recap of a long meeting or a series of videos
- You need view analytics on the video library for a report
Not a fit when
- You have no TeamStream account or workspace access: without it the server will not connect
- Your MCP client cannot reach a remote HTTP server directly: Claude Desktop needs the mcp-remote wrapper
Example request
Find last week's feature launch call in TeamStream and summarize what was decidedLimitations
Official materials do not disclose the full tool list and parameters, only the scenarios are documented: search, transcripts, summaries, metadata, analytics. The MCP key is created in TeamStream settings and must stay in the active status, a revoked key stops working immediately. Claude Desktop cannot connect to the remote server directly, it needs the mcp-remote intermediary process.
How to disable. Revoke the MCP key in MWS TeamStream settings and remove the server from your MCP client configuration.
MCP
- Transport
- http
- Authentication
- API key
| Environment variables | |
|---|---|
| TEAMSTREAM_TOKEN required, secret | TeamStream MCP key in the mcp_sk_live format, issued in the service settings |
Security check
- The key grants access to the company's internal meeting recordings and workspaces
- The server only reads the video library, it does not publish or delete recordings
README in short
MWS's Habr article and MTS support docs describe TeamStream MCP as a way to work with the video library from familiar AI tools: address https://mcp.teamstream.mws.ru/, Bearer-token authorization in the mcp_sk_live format issued in the TeamStream account. They show configuration examples for Cursor directly and for Claude Desktop through mcp-remote. Listed usage scenarios include finding video by meaning, getting transcripts and summaries, working with metadata, and view analytics.
FAQ
Which AI tools are supported?
Official examples show Cursor directly and Claude Desktop through the mcp-remote wrapper, the docs also mention compatibility with Qwen.
What if the key does not work?
Check that it is in the active status: the server immediately stops accepting a revoked key.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI