ChatATP Studio MCP Server
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., "@ChatATP Studio MCP Servercreate a new agent called 'Sales Bot' with a system prompt"
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.
ChatATP Studio MCP Server
Remote FastMCP server that turns the Studio Django /dapi/ API into MCP tools.
Public URL this project is built for:
https://mcp.chat-atp.com/studio/mcpClients (Cursor, Claude, Copilot, ChatATP agents) connect there over Streamable HTTP. Every tool call is proxied to your existing backend with the caller's Authorization header.
What you get
Action-oriented tools over:
Agents (
list_agents,create_agent,preview_agent, ...)Knowledge bases + agent attachments
MCP server definitions + connections
HTTP API tools +
execute_http_api_connectionLLM providers + API-key configs
Messaging platforms
Teams / whoami
Deletes and disconnects require confirm=true.
Related MCP server: mcp_sdk_eyra_accelerator_v15
Local run
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 8000Check:
curl http://localhost:8000/healthMCP endpoint:
http://localhost:8000/studio/mcpAuth
Preferred: the MCP client sends
Authorization: Bearer <studio jwt or chatatp_sk_...>
The server forwards that header to/dapi/.Fallback:
STUDIO_TOKEN/STUDIO_API_KEYin the environment (single-tenant / internal).
Do not bake customer tokens into the image.
Deploy at mcp.chat-atp.com/studio/mcp
Point the mcp.chat-atp.com host at this service with the path intact.MCP_PATH defaults to /studio/mcp, so the process should own the hostname (or receive /studio/mcp unstripped).
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
This repo includes render.yaml. After deploy, put Cloudflare / DNS:
mcp.chat-atp.com → <your-render-service>.onrender.comIf you already have something else on mcp.chat-atp.com and only want /studio/* here, reverse-proxy without stripping the prefix:
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:
mcp.chat-atp.com {
reverse_proxy /studio/* localhost:8000
reverse_proxy /health localhost:8000
}If your proxy strips /studio, set MCP_PATH=/mcp so the public URL is still /studio/mcp after the strip. Do not do both.
Connect a client
Cursor / Claude Desktop / any Streamable HTTP MCP client:
{
"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 | Default | Purpose |
| Render backend URL | Django base URL |
| empty | Fallback auth |
|
| Public MCP path |
|
| Listen port |
|
| Upstream timeout seconds |
|
| Stateless Streamable HTTP (good behind load balancers) |
Notes
Paths marked inferred in the Studio CLI (
/dapi/mcp/servers/,/dapi/http-api/tools/,/dapi/llm/configs/, agent preview) live instudio_mcp/endpoints.py. If a route 404s, change only that file.Document upload is not exposed yet (multipart). Add a dedicated tool when you want file ingest from MCP.
Copilot assistant endpoints (
/dapi/assistant/...) are intentionally not wrapped so this server does not recurse into Copilot.
This server cannot be deployed
Maintenance
Related MCP Connectors
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.
Remote MCP server exposing SMI Aware tools, resources, and skills over 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.-
- FlicenseNot gradedqualityDmaintenanceA standalone MCP server that exposes API endpoints as tools for AI assistants, using SSE transport.-
- AlicenseAqualityDmaintenanceEnables 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.-