TTI-O MCP Server
DTW-Thalion/TTIO-MCP-Server
Gateway MCP para workbench computacional com autenticação e transferência criptografada
Ver no GitHubServidor MCP que expõe acesso não-administrativo a uma instância tti-workbench-server, permitindo que clientes LLM gerenciem containers, cohorts, jobs, sessões, transferências e datasets através de 28 ferramentas organizadas em sete domínios. Funciona como cliente regular do workbench, mantendo token de sessão em memória e comunicando via REST/WebSocket, sem necessidade de arquivos `.tio` locais.
Instalação
npx convez-ai DTW-Thalion/TTIO-MCP-Server1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automação de pipelines de processamento de dados via LLM
- Gerenciamento remoto de containers e sessões computacionais
- Integração de análise de dados com criptografia pós-quântica
Veredito

Ferramenta especializada e bem-estruturada para integração com infraestrutura computacional Thalion. Requer ambiente completo (workbench-server v1.1.0+) e conhecimento técnico profundo; excelente para equipes que já usam a plataforma TTI.
README
A tradução para o português deste README ainda está na fila.
TTI-O MCP Server
An MCP server that gives LLM clients
non-admin access to a running
tti-workbench-server
instance. The server acts as a regular workbench client — it holds a
session token in memory, calls the workbench REST/WebSocket API on behalf
of the LLM, and never requires local .tio files to use the main
container/cohort/job/session tools.
What it exposes
28 tools across seven domains:
| Domain | Tools |
|---|---|
| Auth | ttio_login, ttio_whoami, ttio_logout, ttio_connection_status |
| Containers | ttio_containers_list, ttio_container_get, ttio_container_layers, ttio_container_manifest |
| Cohorts | ttio_cohort_query, ttio_cohort_preview_count |
| Jobs / Pipelines | ttio_job_submit, ttio_jobs_list, ttio_job_get, ttio_job_cancel, ttio_job_events, ttio_pipelines_list, ttio_pipeline_get |
| Sessions | ttio_session_create, ttio_sessions_list, ttio_session_get, ttio_session_terminate, ttio_session_attach_url |
| Transfers | ttio_upload, ttio_download, ttio_federation_peers |
| Data | ttio_dataset_summary, ttio_dataset_read, ttio_dataset_export |
Transfer encryption modes: plain, byok (caller-key AES-256-GCM),
server-kek (HSM-wrapped DEK), pqc (ML-KEM-1024, preview-gated).
Data tools read a local .tio file (e.g. one fetched via
ttio_download). Summaries are returned inline; full signal arrays use
ttio_dataset_export (parquet / csv / json).
Admin capabilities (user management, groups, operations dashboard, KEK rotation, pipeline registration) and container delete are intentionally not exposed.
Requirements
- Python 3.11 or 3.12
- A reachable
tti-workbench-serverinstance (v1.1.0 or later)
Install
ttio-mcp ships from this repository (it is not published to PyPI). Install the
pinned v0.9.0 release with pip:
pip install "ttio-mcp @ git+https://github.com/DTW-Thalion/TTIO-MCP-Server.git@v0.9.0"
This installs the ttio-mcp console script and pulls its pinned
ttio[network,crypto] dependency. To enable the optional transfer extras —
post-quantum (pqc, ML-KEM-1024) and remote-.tio URLs (cloud) — request
them by name:
pip install "ttio-mcp[pqc] @ git+https://github.com/DTW-Thalion/TTIO-MCP-Server.git@v0.9.0"
Installing builds the
ttioSDK from source, sogitand a C toolchain (e.g.build-essentialon Debian/Ubuntu, the Xcode Command Line Tools on macOS) must be available.
From a clone (development)
git clone https://github.com/DTW-Thalion/TTIO-MCP-Server.git
cd TTIO-MCP-Server
git checkout v0.9.0
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -e ".[dev]"
Quickstart
1. Configure
# Required: URL of your workbench server
export TTIO_WB_URL="https://wb.example.com:18443"
# Optional: API key for headless auto-connect (no login call needed)
export TTIO_WB_TOKEN="ttiowbk_abc123..."
2. Run
ttio-mcp
Wire up with Claude Code:
claude mcp add ttio-mcp -- ttio-mcp
3. Connect
Interactive — call ttio_login from the LLM after the server starts:
// tool call: ttio_login
{"username": "alice", "password": "...", "totp": "123456"}
Headless — if TTIO_WB_URL and TTIO_WB_TOKEN are both set, the
server auto-connects at startup and no login call is needed.
Check status at any time with ttio_connection_status or ttio_whoami.
Configuration reference
| Env var | Default | Purpose |
|---|---|---|
TTIO_WB_URL | (required) | Workbench server URL. |
TTIO_WB_TOKEN | (unset) | API key or bearer token for headless auto-connect. |
TTIO_WB_USERNAME | (unset) | Optional username label (informational). |
TTIO_MCP_EXPORT_DIR | ~/.local/state/ttio-mcp/exports | Directory for ttio_dataset_export output. |
TTIO_MCP_CACHE_DIR | ~/.local/state/ttio-mcp/cache | Directory for intermediate cache files. |
TTIO_MCP_PAGE_SIZE | 100 | Default container list page size. |
TTIO_MCP_TRANSPORT | stdio | stdio (default) or http (streamable-HTTP remote connector). |
TTIO_MCP_HTTP_HOST | 127.0.0.1 | Bind address for HTTP transport. |
TTIO_MCP_HTTP_PORT | 8000 | Bind port for HTTP transport. |
TTIO_MCP_HTTP_PATH | /mcp | MCP endpoint path for HTTP transport. |
OAuth resource-server mode (HTTP transport only) — set TTIO_MCP_OAUTH_ISSUER to enable:
| Env var | Default | Purpose |
|---|---|---|
TTIO_MCP_OAUTH_ISSUER | (unset) | Keycloak realm URL. Setting this enables OAuth mode. |
TTIO_MCP_OAUTH_RESOURCE_URL | (unset) | Public URL of this server's /mcp endpoint (reported in RFC 9728 metadata). |
TTIO_MCP_OAUTH_JWKS_URL | (unset) | Keycloak JWKS endpoint for token validation. |
TTIO_MCP_OAUTH_TOKEN_URL | (unset) | Keycloak token endpoint for RFC 8693 exchange. |
TTIO_MCP_OAUTH_CLIENT_ID | (unset) | Client ID for ttio-mcp in Keycloak. |
TTIO_MCP_OAUTH_CLIENT_SECRET | (unset) | Client secret for the above client. |
TTIO_MCP_OAUTH_AUDIENCE | ttio-mcp | Expected aud claim in inbound user tokens. |
TTIO_MCP_OAUTH_EXCHANGE_AUDIENCE | tti-workbench | Target audience for the RFC 8693 exchange (workbench token). |
In OAuth mode the server validates each bearer token (aud=ttio-mcp, scope ttio.connector),
serves GET /.well-known/oauth-protected-resource/mcp (RFC 9728), and exchanges the user token
for a tti-workbench token to build a per-session workbench client. No TTIO_WB_TOKEN needed.
Details: docs/configuration.md.
Full tool catalog: docs/tools.md.
Development
pytest -q # 88 passed, 17 skipped expected
ruff check src tests
CI runs the same commands across Python 3.11 and 3.12 on Ubuntu
(.github/workflows/ci.yml). The 17 skipped tests are the opt-in live
integration suite — enable them with TTIO_MCP_LIVE=1 against a running
workbench server (see tests/integration/test_live_smoke.py).
License
Apache-2.0 — see LICENSE.