TeamDesk MCP Server
MCP (Model Context Protocol) server for TeamDesk databases. Connects Claude (web, Desktop, and mobile), Claude Code, or any MCP-compatible client to the TeamDesk REST API v2.
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
MCP (Model Context Protocol) server for TeamDesk databases. Connects Claude (web, Desktop, and mobile), Claude Code, or any MCP-compatible client to the TeamDesk REST API v2.
TeamDesk MCP Server v2 - Model Context Protocol server for TeamDesk database integration
server.py) — runs on user's machine via stdiodeploy/server_sse.py) — multi-user server with OAuth 2.0, Streamable HTTP, rate limiting, and cachingteamdesk.net/secure/db/XXXXX)No local installation required. Connect directly from claude.ai — works on web, Desktop, and mobile automatically.
When you add a custom connector on claude.ai, it syncs to Claude Desktop and mobile automatically. One setup covers all platforms.
TeamDesk) and the server URL: https://your-server.com/m/{your_key}/sseinstall.bat, server.py, and requirements.txt from this repoinstall.batgit clone https://github.com/Danielbluz/teamdesk-mcp-v2.git
cd teamdesk-mcp-v2
bash install.sh
git clone https://github.com/Danielbluz/teamdesk-mcp-v2.git
cd teamdesk-mcp-v2
pip install -r requirements.txt
Then add to your client config (see next section).
Edit claude_desktop_config.json:
%APPDATA%\Claude\claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"teamdesk": {
"command": "python",
"args": ["C:\\path\\to\\server.py"],
"env": {
"TEAMDESK_API_TOKEN": "your_token_here",
"TEAMDESK_DATABASE_ID": "your_database_id"
}
}
}
}
Add to .claude/.mcp.json in your project or ~/.claude/.mcp.json globally:
{
"mcpServers": {
"teamdesk": {
"command": "python",
"args": ["C:\\path\\to\\server.py"],
"env": {
"TEAMDESK_API_TOKEN": "your_token_here",
"TEAMDESK_DATABASE_ID": "your_database_id"
}
}
}
}
.env fileInstead of setting env vars in the config, you can create a .env file next to server.py:
cp .env.example .env
# Edit .env with your credentials
[Status] = 'Ativo'
[Amount] > 1000
Contains([Name], 'Solar')
[Date] >= ToDate('2026-01-01')
Column -- ascending (default)
Column//DESC -- descending
These are undocumented behaviors that this server handles correctly:
python is in your PATH: python --version[TeamDesk MCP]TEAMDESK_API_TOKEN and TEAMDESK_TOKEN (legacy) are acceptedThe deploy/ folder contains server_sse.py — a multi-user remote MCP server designed for deployment on a VPS behind Nginx/TLS. It supports:
Admin creates a record in the Acesso table (TeamDesk) with:
Chave_MCP: unique key for the user (e.g., john_company_2026)Token: the user's TeamDesk API tokenAtivo_MCP: Sim (to enable access)Each user gets a personal endpoint: https://your-server.com/m/{chave}/sse
The server validates the key, retrieves the user's token, and proxies all MCP tool calls to the TeamDesk API using that token.
claude.ai requires these OAuth endpoints for custom connectors:
Accept: application/json, text/event-stream header if missing (claude.ai sometimes omits it, causing 406 from MCP SDK)stateless=False) — required for persistent Mcp-Session-Iddeploy/docker-compose.yml)cd deploy
cp .env.example .env
# Edit .env with your TEAMDESK_DATABASE_ID, TEAMDESK_MASTER_TOKEN, MCP_PUBLIC_URL
docker compose up -d
When a user configures a custom connector on claude.ai (web), it automatically becomes available on Claude Desktop and Claude mobile — no separate configuration needed. The connector is linked to the user's Anthropic account, not to a specific app.
This means: one setup on the web covers all platforms.
MIT
TeamDesk MCP Server v2 - Model Context Protocol server for TeamDesk database integration
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Teamdesk MCP V2 roda localmente via stdio.
Última verificação: 2026-10-28. TeamDesk MCP Server v2 - Model Context Protocol server for TeamDesk database integration