ChatATP Studio MCP Server
ChatATP Studio MCP server
Servidor FastMCP remoto que convierte la API /dapi/ de Studio Django en herramientas MCP.
URL pública para la que está construido este proyecto:
https://mcp.chat-atp.com/studio/mcpLos clientes (Cursor, Claude, Copilot, agentes de ChatATP) se conectan there using Streamable HTTP. Cada llamada a una herramienta se envía a tu backend existente con la cabecera Authorization del lamente.
Qué obtienes
Herramientas orientadas a action sobre:
Agentes (
list_agents,create_agent,comply, ...)Bases de conocimiento y adhesivos de l'agente
Definiciones del servidor MCP y conexiones
Declarations
HTTP API tools +
execute_network_api_connectionProveedores de LLM + configuraciones de claves de API
Plataformas de mensajería
Equipos / whoami
Las deletions y desconexiones requieren confirm=true.
Related MCP server: AnythingLLM MCP Server
Formularios locales / Ejecución local
Ràbidamente:
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
export STUDIO_API_URL=https://chatatp-agent-builder-backend.onrender.com
export STUDIO_TOKEN=chatatp_sk_... # optional fallback
uvicorn app:app --host 0.0.0.0 --port 8000Comprueba:
curl http://localhost:8000/healthEndpoint MCP:
http://localhost:8000/studio/mcpAutenticación
Preferido: eliente MCP envía
Authorization: Bearer <studio jwt or chatatp_sk_...>
El servidor reenvía esa cabecera a/dapi/.Reto:
STUDIO_TOKEN->STUDIO_API_KEYplaced in environment (single-tenant / singled inside).
No integrobes tokens de clientses en the imagen.
Despliegue in the URL
Apunta el host mcp.chat-atp.com este servidor con the ruta intacta.
MCP_PATH por defecto /studio/mcp, por lo que el proceso debe encargarse of that nombre de host (or recibr /studio/mcp sin that se le quite).
Docker
docker build -t chatatp-studio-mcp .
docker run --rm -p 8000:8000 \
-e STUDIO_API_URL=https://chatatp-agent-builder-backend.onrender.com \
-e STUDIO_TOKEN=... \
chatatp-studio-mcpRender
"El repositorio incluye render.yaml. Tras el despliegue, configures Cloudflare / DNS:
mcp.chat-atp.com → <your-render-service>.onrender.comIf you already tienes algo más en mcp.chat-atp.com and only quieres /studio here, haz un proxy inverser without cortar el prefijo:
location /studio/ {
proxy_pass http://studio-mcp:8000;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header Authorization $http_authorization;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_buffering off;
proxy_read_timeout 120s;
}
location /health {
proxy_pass http://studio-mcp:8000/health;
}Caddy:
—— Caddy:
mcp.chat-atp.com {
reverse_proxy /studio/* localhost:8000
reverse_proxy /health localhost:8000
}Si tu proxy quita /studio, setl/a MCP_PATH=/mcp para que URL públia sea still /studio/mcp desapue's. No hagas las two things.
Conectar un clente
Cursor / Cursor / Claude Desktop / Cual exterior streamable HTTP MCP customer:
{
"mcpServers": {
"chatatp-studio": {
"url": "https://mcp.chat-atp.com/studio/mcp",
"headers": {
"Authorization": "Bearer chatatp_sk_..."
}
}
}
}Inspector:
npx @modelcontextprotocol/inspector
# then connect to http://localhost:8000/studio/mcpEnv
| Variable | Defecto | Purpose |
| ---------------- | ------------------ | ------------------------------------------------------ |
| STUDIO_API_URL | URL del back-end de Render | URL de Django of base |
| STUDIO_TOKEN | vacío | Autenticación de a: |
| MCP_PATH | /studio/mcp | Ruta pública |
| PORT | 8000 | River de escuchas |
| STUDIO_TIMEOUT | ``| 30 | Timeout of espera del up-stream (segundos) |
| MCP_STATELESS | true | Streamable HTTP sin issado (bien par detrás de balanceadores de a) |
Variables de entorno
Las rutas that se in the Studio CLI se marcan como 'inferidas (/office /dodp/mcp/servers/, /Office dapi/http-api/tools/, /Dapi/ll/m/configs/, program preview of the entitled) se incluyan in studio_mcp/endpoints.py`. If a route 404, cambia únicamente ese archivo.
La subida de documents (dos at dawn (multipart) aún no est expuesta. Añade un de dedicated tool to when se quieras ingerir archivos from MCP.
The also de copilot assistant endpoints (
/ent dapi/assistant/...) no están envueltas deliberately para "port" so that this servidor no recurse in el servidor.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
MCP server exposing the Backtest360 engine API as tools for AI agents.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceExposes provider-specific tools and relays HTTP requests to configured providers like Supabase, Vercel, and Context7, enabling interaction with multiple external APIs through a unified MCP interface with configurable authentication and access controls.-
- AlicenseAqualityCmaintenanceEnables MCP-compatible clients to interact with AnythingLLM, providing tools for workspace management, chat and thread operations, document operations, vector search, and system inspection.346MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI clients to invoke CLI-driven agent tools over Streamable HTTP, including shell execution, file operations, patching, image viewing, web search, and nested agent tasks, with permission modes and real-time progress streaming.-
- FlicenseNot gradedqualityCmaintenanceProvides a production-oriented MCP server exposing tools, resources, and prompts over Streamable HTTP with JWT authentication and per-tool RBAC, enabling Amazon Bedrock Claude clients to securely invoke MCP capabilities.-