Start here. Returns the step-by-step workflow, the current login state and where files go.

Open the Innoslate project in a browser window and wait until the user is logged in.

project_url: the address bar of the project, https:////p//... wait_seconds: how long to wait for the user to finish logging in (default 300). If INNOSLATE_USERNAME and INNOSLATE_PASSWORD are set in the environment or in ~/.innoslate-mcp/.env, they are typed into the login form automatically. Passwords are never accepted as tool arguments.

Is the browser running, which project is current, is the login still valid.

Survey the whole project before any write. Run once per project, and again after big changes.

Reads every entity, the schema, review comments and members, then writes PROJECT_MAP.md, NOMENCLATURE.md and snapshot.json into the project workspace. guides_dir is a folder (or one file) with the instructor's guide documents (PDF, DOCX, ...); their text is saved under guides/ and the numbering patterns they mention are compared with what the project uses. Returns a summary. Read the full files with innoslate_read_workspace.

Read a file from the project workspace: "map" (PROJECT_MAP.md), "nomenclature", "audit" (the write log) or a relative path such as "guides/Deliverable_2.txt". Long files come in pages: pass next_offset back as offset.

The project's classes, relations (with inverses), labels and properties.

kind: all | classes | relations | labels | properties class_name: restrict labels and properties to one class (e.g. "Requirement").

Search entities. Combine any filters: text (words in name or description), class_name, label, number (exact), number_prefix (e.g. "SR.1."), document (id, number or name: only items inside it). Returns short rows; use innoslate_get for one entity in full.

One entity in full: text, labels, attributes, and every relation with the target's number and name. ref is an id, or a number. A number can match several entities (numbers repeat in Innoslate), so every match is returned with the documents it sits in.

Everything inside a document, in order, with depth, text, labels and trace links. document is an id, a number (e.g. "UN.1") or the exact name.

Review comments on the project (often the marker's feedback), with the entity each is on.

List the files in a local folder the user pointed at, with size and whether they can be read.

Plain text of a local document: PDF, DOCX (tables kept), XLSX, PPTX, CSV, JSON, Markdown, TXT, VTT/SRT transcripts. Long files come in pages: pass next_offset back as offset. Audio and video need a transcript first.

Check requirement wording before writing it (or check a document already in Innoslate).

items: [{"number", "name", "text", "rationale"?}] or document: id, number or name. extra_banned: {"regex": "why"} for course-specific rules, e.g. {"\bfacial\b": "no worker identification"}. Errors should be fixed before innoslate_apply; warnings need a human look.

Create or update entities and relations in one save, then read everything back to verify.

Always call with dry_run=true first. It returns a summary and a confirm_token. Show the user, and only after their yes call again with the identical plan, dry_run=false and the token.

plan = { "update_existing": false, # true lets matched existing items be changed "entities": [{ "key": "sr", # your name for it inside this plan "class": "Artifact", "number": "SR.1", "name": "Stakeholder Requirements", "labels": ["Requirements Document"], "description": "plain text" # or description_html }, { "key": "sr1", "class": "Requirement", "number": "SR.1.1", "name": "Live view", "description": "The system shall ...", "labels": ["Functional Requirement"], "attributes": {"Rationale": "..."}, # property names from innoslate_schema "document": "sr", # top-level item of that document "parent": null, # or a ref: nested under that item (decomposes) "relations": {"traced from": [{"number": "UN.1.3", "document": "UN.1"}]} }], "relations": [{"from": "sr1", "relation": "verified by", "to": 12345}], "unlink": [{"from": 111, "relation": "traced to", "to": 222}] } A ref is a plan key, an id, {"number": ..., "document": } or {"number"/"name", "class"}. Existing items are matched by number inside their document only. Every relation is written on both sides. Nothing is deleted. id targets one existing entity directly.

Change one existing entity by id. fields may hold name, number, description, description_html, labels (replaces), add_labels, attributes, relations, parent, document. Same dry-run and confirm_token flow as innoslate_apply.

Upload a local file and put it in an entity's file property (on Artifacts this is "File"). Replaces a file already there. Same dry-run and confirm_token flow as innoslate_apply.

Run Innoslate's own Quality Check on a requirements document (UI: More > Quality Check) and return each requirement's Quality Score and the checks it failed, lowest first. Innoslate stores the scores on the requirements; nothing else changes.

Download one of Innoslate's document reports (UI: Reports > > Create), e.g. "Basic Document Output (DOCX)" or "RTM Output (XLSX)". If the name is wrong, the reply lists the reports this document offers. Saved under the workspace's reports/ folder unless out_dir is given.