DEVELOPERS
MCP integration.
Connect Claude, ChatGPT, Gemini, or any other MCP-aware client to your KiteOS workspace for read-only access to your projects, tasks, and videos. This endpoint borrows the tool-discovery and tool-call concepts from Anthropic's Model Context Protocol — a simplified HTTP interface, not a wire-compatible MCP server. See “Connect an AI client” below for what that means in practice.
Getting started
Every request needs an API token scoped to what it's allowed to read. Generate a token from your account settings — it's shown to you exactly once, so copy it somewhere safe before you navigate away.
Endpoint
One URL handles both tool discovery and tool calls. Send your token as a bearer token on every request.
https://creativedesk.online/api/mcpAvailable tools
GET the endpoint to list tools and their input schemas. POST to call one. A token can only call a tool if it was granted that tool's scope.
List your projects. An admin's token lists every project in the workspace; an editor's the projects that hold a task assigned to them; a cameraman's the projects they have a shoot on.
No parameters.
List tasks, optionally filtered by project or status. An admin's token lists the whole workspace's; an editor's only the tasks assigned to them. Not available to a cameraman's token.
List videos, optionally filtered by client. Scoped to the token owner like list_tasks.
Try it with curl
curl https://creativedesk.online/api/mcp \ -H "Authorization: Bearer kite_pat_xxxxxxxx"
curl -X POST https://creativedesk.online/api/mcp \
-H "Authorization: Bearer kite_pat_xxxxxxxx" \
-H "Content-Type: application/json" \
-d '{"tool": "list_projects", "params": {}}'Connect an AI client
This endpoint speaks a simplified, KiteOS-specific interface inspired by MCP — it does not implement MCP's full JSON-RPC 2.0 / stdio / Streamable-HTTP wire protocol. The snippets below are illustrative starting points for pointing an MCP-capable client at this URL and token, not verified, drop-in configs for any vendor's native MCP support. Treat them as a template to adapt, and expect to do some wiring on the client side.
{
"mcpServers": {
"kiteos": {
"url": "https://creativedesk.online/api/mcp",
"headers": {
"Authorization": "Bearer kite_pat_xxxxxxxx"
}
}
}
}Server URL: https://creativedesk.online/api/mcp Auth type: Bearer token Token: kite_pat_xxxxxxxx
endpoint: https://creativedesk.online/api/mcp auth: type: bearer token: kite_pat_xxxxxxxx
For the full Model Context Protocol specification this interface takes its concepts from, see modelcontextprotocol.io.
← Back to home