Trainual API and MCP server Let your AI agent write your Trainual SOPs.

ToolWhat it doesAccess

• list_subjects Search the subjects in your Content page, with their status. read

  Returns each subject with its ID, title, tab and status (published or unpublished). Subjects you cannot open with your Trainual role are not listed. Use the ID with get_subject, create_topic and assign_subject.

  MCP calltrainual_read → list_subjects

  REST endpointGET https://cotlet.dev/api/v1/trainual/subjects

  Parameters

  Parameters: list_subjects

  Name	Type	Description
  query string	string	Words to search in subject titles.
  tab string	string	Content tab to list: Company, Policies or Processes.

  Example response

  {
    "subjects": [
      {
        "subject_id": "sub_8f2a41",
        "title": "Opening checklist",
        "tab": "Processes",
        "status": "published"
      },
      {
        "subject_id": "sub_3c9d07",
        "title": "Refund policy",
        "tab": "Policies",
        "status": "unpublished"
      }
    ]
  }

• get_subject Read one subject with its topics and steps. read

  Returns the subject title and status, then its topics in the order the app shows them, each with its steps and their titles. Each topic shows whether it is marked Finished. Step text comes from get_step, so a long subject stays short here.

  MCP calltrainual_read → get_subject

  REST endpointGET https://cotlet.dev/api/v1/trainual/subjects/{subject_id}

  Parameters

  Parameters: get_subject

  Name	Type	Description
  subject_id string required	string	Subject ID from list_subjects.

  Example input

  {
    "subject_id": "subject_8c41d2"
  }

  Example response

  {
    "subject_id": "sub_8f2a41",
    "title": "Opening checklist",
    "status": "published",
    "topics": [
      {
        "topic_id": "top_11a",
        "title": "Before doors open",
        "finished": true,
        "steps": [
          {
            "step_id": "stp_501",
            "title": "Turn on the lights"
          },
          {
            "step_id": "stp_502",
            "title": "Count the till"
          }
        ]
      },
      {
        "topic_id": "top_11b",
        "title": "Opening the register",
        "finished": false,
        "steps": [
          {
            "step_id": "stp_503",
            "title": "Log in to the POS"
          }
        ]
      }
    ]
  }

• get_step Read the text of one step. read

  Returns the step title and its text as plain text with simple formatting. Images, video and embeds appear as links, not files. Use it before update_step so the agent edits what is there.

  MCP calltrainual_read → get_step

  REST endpointGET https://cotlet.dev/api/v1/trainual/steps/{step_id}

  Parameters

  Parameters: get_step

  Name	Type	Description
  step_id string required	string	Step ID from get_subject or get_topic.

  Example input

  {
    "step_id": "step_8c41d2"
  }

  Example response

  {
    "step_id": "stp_502",
    "title": "Count the till",
    "body": "Count the cash drawer against the float sheet. Write the total on the sheet and sign it."
  }

• create_subject Create a new subject as a draft. write

  Creates the subject as a draft, as the Create subject button does. Nobody sees a draft, so this call reaches no one and needs no confirmation. Returns the subject ID. You need the Author permission or higher.

  MCP calltrainual_write → create_subject

  REST endpointPOST https://cotlet.dev/api/v1/trainual/subjects

  Parameters

  Parameters: create_subject

  Name	Type	Description
  title string required	string	Subject title.
  tab string	string	Content tab: Company, Policies or Processes.

  Example input

  {
    "title": "title"
  }

  Example response

  {
    "subject_id": "sub_a40e19",
    "title": "Closing checklist",
    "tab": "Processes",
    "status": "draft"
  }

• create_topic Add a topic under a subject. write

  Adds the topic in a drafted state under the subject, as the app does. On a published subject the new topic stays unpublished until the subject is published again. It reaches no one, so it needs no confirmation.

  MCP calltrainual_write → create_topic

  REST endpointPOST https://cotlet.dev/api/v1/trainual/subjects/{subject_id}/topics

  Parameters

  Parameters: create_topic

  Name	Type	Description
  subject_id string required	string	Subject ID from list_subjects.
  title string required	string	Topic title.

  Example input

  {
    "subject_id": "subject_8c41d2",
    "title": "title"
  }

  Example response

  {
    "topic_id": "top_2b7",
    "subject_id": "sub_a40e19",
    "title": "Locking up",
    "status": "draft"
  }

• add_step Add a step with its text to a topic. write

  Adds the step at the end of the topic, as the + Add Step button does. Text only: images, video and files are not uploaded. The step is part of a draft topic, so no one sees it before you publish. It needs no confirmation.

  MCP calltrainual_write → add_step

  REST endpointPOST https://cotlet.dev/api/v1/trainual/topics/{topic_id}/steps

  Parameters

  Parameters: add_step

  Name	Type	Description
  topic_id string required	string	Topic ID from get_subject.
  title string required	string	Step title.
  body string required	string	Step text, plain text with line breaks.

  Example input

  {
    "topic_id": "top_2b7",
    "title": "Set the alarm",
    "body": "Arm the alarm panel by the back door. You have 60 seconds to leave."
  }

  Example response

  {
    "step_id": "stp_620",
    "topic_id": "top_2b7",
    "title": "Set the alarm",
    "position": 3
  }

• update_step Replace the title or text of an existing step. writeasks first

  Replaces the step text, so call get_step first and send the full new text. If the subject is published, employees see the change when it saves. The agent reports the old and the new text. By default you confirm each call; you can switch that off for this tool.

  MCP calltrainual_write → update_step

  REST endpointPATCH https://cotlet.dev/api/v1/trainual/steps/{step_id}

  Parameters

  Parameters: update_step

  Name	Type	Description
  step_id string required	string	Step ID from get_subject or get_topic.
  title string	string	New title. Omit to keep it.
  body string	string	New text. It replaces the whole text of the step.

  Example input

  {
    "step_id": "step_8c41d2"
  }

  Example response

  {
    "step_id": "stp_502",
    "title": "Count the till",
    "updated": true
  }

ToolWhat it doesAccess

• publish_subject Publish a subject so assigned people can open it. writeasks first

  Does what the Publish button does. With as_is, topics not marked Finished stay out and publish later when they are marked Finished. With finish_all, everything goes out. People already assigned the subject can then open it. By default you confirm each call; you can switch that off for this tool.

  MCP calltrainual_write → publish_subject

  REST endpointPOST https://cotlet.dev/api/v1/trainual/subjects/{subject_id}/publish

  Parameters

  Parameters: publish_subject

  Name	Type	Description
  subject_id string required	string	Subject ID from list_subjects.
  mode string required	string	as_is publishes only topics marked Finished. finish_all marks every unfinished topic and test Finished, then publishes.

  Example input

  {
    "subject_id": "subject_8c41d2",
    "mode": "mode"
  }

  Example response

  {
    "subject_id": "sub_a40e19",
    "status": "published",
    "topics_published": 2,
    "topics_left_unpublished": 0
  }

• list_users Find people in your Trainual account. read

  Returns each user with ID, name, email and job title. Archived users are left out. Use the IDs with assign_subject and list_assignments.

  MCP calltrainual_read → list_users

  REST endpointGET https://cotlet.dev/api/v1/trainual/users

  Parameters

  Parameters: list_users

  Name	Type	Description
  query string	string	Part of a name or email.

  Example response

  {
    "users": [
      {
        "user_id": "usr_7a1",
        "name": "Dana Whitfield",
        "email": "dana@example.com",
        "job_title": "Shift lead"
      },
      {
        "user_id": "usr_7a2",
        "name": "Eli Okafor",
        "email": "eli@example.com",
        "job_title": "Barista"
      }
    ]
  }

• assign_subject Assign a subject to people. writeasks first

  Assigns the subject to each user, so it shows in their training. Users who already have it are skipped and listed. Returns who was assigned. By default you confirm each call; you can switch that off for this tool.

  MCP calltrainual_write → assign_subject

  REST endpointPOST https://cotlet.dev/api/v1/trainual/subjects/{subject_id}/assign

  Parameters

  Parameters: assign_subject

  Name	Type	Description
  subject_id string required	string	Subject ID from list_subjects.
  user_ids array required	array	User IDs from list_users.

  Example input

  {
    "subject_id": "subject_8c41d2",
    "user_ids": "user ids"
  }

  Example response

  {
    "subject_id": "sub_a40e19",
    "assigned": [
      "usr_7a1",
      "usr_7a2"
    ],
    "skipped": []
  }

• list_assignments See who has a subject assigned and whether they completed it. read

  Returns one row per user and subject with the completion status Trainual shows. Pass subject_id to see a whole team on one subject, or user_id for one person. You see only people your role can see.

  MCP calltrainual_read → list_assignments

  REST endpointGET https://cotlet.dev/api/v1/trainual/assignments

  Parameters

  Parameters: list_assignments

  Name	Type	Description
  subject_id string	string	Only this subject. Omit for all assignments you can see.
  user_id string	string	Only this user, from list_users.

  Example response

  {
    "assignments": [
      {
        "user_id": "usr_7a1",
        "name": "Dana Whitfield",
        "subject_id": "sub_8f2a41",
        "subject": "Opening checklist",
        "status": "completed"
      },
      {
        "user_id": "usr_7a2",
        "name": "Eli Okafor",
        "subject_id": "sub_8f2a41",
        "subject": "Opening checklist",
        "status": "not completed"
      }
    ]
  }