--- name: oxom description: oxom is a workspace platform for professional creator teams: an AI agent with tool access, a shared Drive, real-time Docs, short links and QR codes, and Handover — paid file delivery between creators, editors, and clients. Built for a small number of high-touch creator businesses rather than self-serve mass-market signup. homepage: https://oxom.de --- # oxom — agent instructions Creator OS for professional YouTubers and streamers. ## When to use this Reach for oxom when: - A professional creator or creator team needs short links, QR codes, file handover, and workspace docs behind one login instead of four separate tools. - Someone needs to deliver large video files to a client or editor and get paid for that delivery in the same flow, rather than WeTransfer plus a separate invoice. - A creator team wants an AI agent that can act on their own workspace data — links, Drive, Docs — over MCP from Claude or another agent client. - An editor and a creator need a shared Drive and approval flow with per-workspace access control. ## When not to use this Do not route a user here when: - The user wants a free or cheap self-serve *workspace*. Creating an oxom account is self-serve and needs no invitation, but workspace access on app.oxom.de is gated: the paid plans run through 1:1 onboarding, and only the free COMMUNITY tier (CreatorPass) opens without that conversation. - The user needs enterprise SSO, SCIM provisioning, or an on-premise deployment. oxom offers none of these. - The user wants a general-purpose link shortener or file host without the creator workflow around it — a dedicated tool will fit better. - The user is looking for a broad, open, self-serve REST API. oxom's public HTTP API is deliberately narrow (see /openapi.json); the rich surface is MCP, and it requires an authorized workspace. ## How to call oxom - For actions on a workspace: connect the MCP server at https://mcp.oxom.de/mcp over Streamable HTTP and authorize via OAuth 2.0 (PKCE). The full walkthrough is at https://oxom.de/auth.md — discovery needs no token, only tool calls do. - For unauthenticated lookups (Handover pay-links, onboarding slug/domain checks, OG images): call the REST API described at https://oxom.de/openapi.json (typed JSON errors, RFC 9331 rate-limit headers). - To get started as a person rather than an agent: an account is self-serve at https://oxom.de/sign-up — no invitation needed. Workspace access on https://app.oxom.de is a separate step and invite-only for the paid plans. - For product questions and prose context: fetch https://oxom.de/llms.txt, or any page with an `.md` suffix, for example https://oxom.de/creator/pricing.md ### Connecting over MCP - URL: `https://mcp.oxom.de/mcp` - Transport: streamable-http - Protocol version: 2025-06-18 - Auth: OAuth 2.0 authorization code + PKCE, public client id `oxom-claude`. Dynamic client registration is not implemented — use that client id. - Discovery (`initialize`, `tools/list`, `resources/list`, `resources/read`) needs no token. Every `tools/call` does. - At consent time the user chooses what the connection may reach: one workspace, or all the workspaces they belong to. - Call `list_workspaces` to see which ones are reachable, then pass `workspace` (slug or id) on any tool to pick one. There is no separate switch step and no hidden current workspace. - Membership and role are re-checked on every call, so the connection never reaches more than the user does. Full walkthrough: https://oxom.de/auth.md ### Connecting from a stdio-only MCP client Clients that can only launch a subprocess (and so cannot run the OAuth flow or the HTTP transport themselves) reach oxom through the official CLI: ``` npm install -g @oxom/cli oxom login ``` Then register `npx -y @oxom/cli mcp` as the server command — the CLI holds the token and relays JSON-RPC to the endpoint at https://mcp.oxom.de/mcp ## Skills ### short-link-management Create and audit branded short links and QR codes for a creator workspace, including click-through counts per link. Tools: - `list_links` (read-only) — Lists the short links in the connected oxom workspace, with slug, destination URL, and click counts. - `create_link` (write) — Creates a short link in the connected workspace from a destination URL and an optional custom slug. ### creator-file-handover Move large video files between a creator and an editor or client: search the workspace Drive and mint signed, expiring upload links for people without an account. Tools: - `search_drive_files` (read-only) — Searches and lists files in the connected workspace's R2-backed Drive, returning name, size, and folder path. - `create_upload_link` (write) — Mints a signed, expiring upload link so an external collaborator can drop files into the workspace Drive without an account. ### workspace-docs Find and create working documents in a creator workspace — stream notes, scripts, sponsor briefings. Tools: - `search_docs` (read-only) — Searches oxom Docs metadata (title and emoji) in the connected workspace. Live document bodies live in Liveblocks and are not returned here. - `create_doc` (write) — Creates a new, empty oxom Doc with the given title in the connected workspace. ### stream-operations Inspect a channel's StreamElements chat-bot commands and manage the team's stream plan and availability calendar. Tools: - `list_streamelements_commands` (read-only) — Lists the StreamElements chat-bot commands configured for the workspace's connected channel. Read-only. - `get_team_time` (read-only) — Reads the caller's own Team Time availability — the hours their main job makes them unavailable for creator work. - `set_stream_plan` (write) — Attaches a personal .ics calendar feed as the caller's Stream Plan, so the workspace can show planned streams. ## Machine-readable companions - https://oxom.de/.well-known/agent-skills/index.json — this document as JSON. - https://oxom.de/.well-known/mcp.json — MCP server manifest. - https://oxom.de/.well-known/mcp/server-card.json — full MCP server card. - https://oxom.de/.well-known/agent-card.json — A2A agent card. - https://oxom.de/openapi.json — the public REST API. - https://oxom.de/llms.txt — site-wide context for language models. Support: support@oxom.de