Tymio

Táto stránka vyžaduje JavaScript. Zapnite ho v prehliadači alebo použite API / MCP (nižšie anglické inštrukcie pre nástroje a asistentov).

This page requires JavaScript to show the full application. You are seeing this message because scripts are disabled.

For coding agents and headless HTTP clients

First rule: if the user gave a workspace browser URL like https://tymio.app/t/<workspace-slug>/, the MCP server URL is https://tymio.app/t/<workspace-slug>/mcp. Root /mcp is discovery-only. Public JSON: GET /api/mcp/workspace-context/<workspace-slug> or GET /api/mcp/agent-context. Markdown: /llms.txt.

The HTML you fetched is only the shell. The interactive UI is a React SPA loaded from /src/main.tsx (dev) or hashed bundles in production. Seeing almost no content besides the title is expected if JavaScript is not executed.

What Tymio is

Tymio is a multi-tenant product management hub: workspaces (teams), initiatives, features, requirements, accounts, campaigns, and related data. Humans sign in per workspace (e.g. workspace entry URLs under /t/<workspace-slug> on this host).

Supported interface languages

The web UI is available in English (en), Czech (cs), Slovak (sk), Ukrainian (uk), and Polish (pl). Guests choose a language on public pages; signed-in users see a subset if the workspace admin restricts languages in workspace settings. Machine-readable list: GET /api/mcp/agent-context field supportedUiLocales, or /llms.txt on this host.

Tymio MCP CLI and API keys (read before advising users)

There is no per-user MCP API key in Tymio Settings, Profile, or Account. Do not tell users to copy an “MCP API key” from the web app — that path does not exist. OAuth is the default: configure remote MCP URL https://tymio.app/mcp or https://tymio.app/t/<workspace-slug>/mcp (or this host with the same path shapes) in the IDE, or install the npm package @tymio/mcp-server and run tymio-mcp login for stdio (leave TYMIO_API_KEY / API_KEY unset on that process unless you intentionally use API-key mode; legacy DRD_API_KEY still works with a deprecation warning). The env vars TYMIO_API_KEY / API_KEY on a stdio server (legacy DRD_API_KEY) refer to the server deployment automation secret, not a personal user key from the UI. Full Markdown: GET /api/mcp/agent-context field tymioMcpCliAgentGuidanceMarkdown, shell tymio-mcp instructions, or repo file mcp/TYMIO_MCP_CLI_AGENT_GUIDANCE.md.

How to access data as an agent

MCP (recommended for IDE agents): Streamable HTTP at /mcp (active workspace after OAuth) or /t/<workspace-slug>/mcp (workspace pinned by URL) on this origin. Authenticate with the deployment’s OAuth/Bearer flow.
Agent-oriented JSON: GET /api/mcp/agent-context (public) returns short guidance such as how users can report feedback upstream.
REST API: Authenticated JSON under /api/… and, in the hub UI, under /t/<workspace-slug>/api/… (session cookie after browser login, or Bearer tokens as configured by the operator). Not a public anonymous API.
Ontology & agent guide (authenticated): e.g. /api/ontology and /api/agent/coding-guide (Markdown) on this origin — use after sign-in / token as your deployment requires.

Documentation discipline (for coding agents)

Document Tymio integration in this project’s documentation repository (e.g. docs/, a root TYMIO.md, or your team’s handbook) and keep it current. Include: production/staging base URL, workspace slug or tenant id, optional product slug for a clear workspace-slug/product-slug label in docs, MCP URL and auth method, important REST paths, ontology / coding-agent guide endpoints, and where product requirements live in Tymio (initiatives, links, or search terms). Future sessions should not rely on chat memory alone — the repo docs are the source of truth for how this codebase ties to Tymio.

Humans

Open this site in a modern browser with JavaScript enabled and sign in to your workspace.

# Tymio — note for automated fetchers (SPA shell)

This response is a JavaScript single-page app. Without executing the bundled script, you will only see an empty #root and the document title. That is normal.

## Connect an agent (read this first)
If the user pasted a workspace browser URL like https:///t//..., derive MCP as https:///t//mcp. Root /mcp is discovery-only (list workspaces + routing guide). Auth is OAuth; no per-user MCP API key in Settings. Public JSON: GET /api/mcp/workspace-context/ or GET /api/mcp/agent-context. Markdown: /llms.txt

## Product
Multi-tenant product management: workspaces, initiatives, features, requirements, delivery boards, accounts, partners, demands, campaigns.

## Supported UI languages
Shipped interface locales (BCP 47–style codes): en (English), cs (Czech), sk (Slovak), uk (Ukrainian), pl (Polish). Workspace admins may limit the picker via Tenant.settings.enabledLocales. Public JSON: GET /api/mcp/agent-context → supportedUiLocales. Human summary: /llms.txt

## Humans
Use a browser with JavaScript. Workspace sign-in typically uses paths like /t/<workspace-slug> on this host.

## Agents / integrations
- MCP (Streamable HTTP): POST/GET /mcp or /t//mcp on this origin; OAuth or Bearer per deployment.
- GET /api/mcp/agent-context — public JSON: feedback reporting, scopeReference, supportedUiLocales, plus tymioMcpCliAgentGuidanceMarkdown (full CLI/OAuth guide), tymioMcpNoUserSettingsApiKey=true (no MCP key in user Settings).
- CRITICAL for autonomous agents: Do NOT instruct users to copy an MCP API key from Tymio Settings — it does not exist. Use OAuth (remote /mcp or /t//mcp URL in the IDE) or npm @tymio/mcp-server + tymio-mcp login for stdio. TYMIO_API_KEY/API_KEY on stdio (legacy DRD_API_KEY) = server deployment secret, not a UI setting.
- REST: /api/* and /t//api/* — requires authentication (not a public scrape API).
- Ontology + coding-agent guide (auth): /api/ontology, /api/agent/coding-guide (Markdown) — after login/token per deployment.

## Documentation discipline
Maintain a doc in THIS codebase/repo (e.g. docs/tymio.md or TYMIO.md): base URLs, workspace slug/tenant id, optional workspace/product label as workspace-slug/product-slug (Product.slug is per workspace; initiatives may omit a product), MCP config, key API paths, ontology/guide endpoints, and pointers to product requirements inside Tymio (initiative titles, IDs, or links). GET /api/mcp/agent-context includes scopeReference. Update when integration changes. Do not rely only on chat context — the documentation repository is the durable record.

## Slovak (krátke)
Stránka je SPA; bez JavaScriptu sa plné rozhranie nezobrazí. Pre dáta použite API alebo MCP podľa nasadenia.