mocop
Browse · Docs · Guide · Analyze

transept

MCP server by Transept · mcp

Transept is a translation workspace: documents are split into blocks, workflows (translate / proofread / review steps) run over them per target language, and results read back per block. The loop: document_create (or strings_import for key-value corpora) → run_estimate (free) → run_start / group_run_start with confirm:true → poll run_get / group_run_get → document_content_get. Multi-language work uses group_* (one lane per language); single-version work uses run_*. Ids — each tool names the one it takes: document_id (a language VERSION; siblings share language_group_id), job_id (a run; from run_start/run_list), group_run_id, processing_job_id (an import; poll processing_job_get), translation.id inside document_content_get blocks (feeds block_translation_update), unit_id (stable string keys, = Figma node ids for Figma docs). Billing is in credits (1 per source word in standard mode, 3 in premium). run_start / group_run_start / run_gate_approve without confirm:true return the estimat…

Endpoint: https://app.transept.ai/api/public/v1/mcp

Verification: observed. Source: crawl.

Capabilities (42)

  • me_get
  • project_list
  • project_create
  • document_list
  • document_get
  • document_create
  • document_update
  • document_delete
  • document_add_languages
  • document_content_get
  • document_attach_resources
  • document_resync_source
  • strings_import
  • strings_reimport
  • block_update
  • block_translation_update
  • processing_job_get
  • workflow_list
  • workflow_template_list
  • run_estimate
  • run_start
  • run_get
  • run_list
  • run_cancel
  • run_gate_approve
About · Contact · Privacy