When you need to hand off research, produce a reproducibility package, or attach a structured summary to a paper appendix, the Export/Import tools let you move Thesis graph state in and out as JSON, generate Markdown or PDF summaries from node trees, and stream long documents without buffering. The Updates and Audit tools complement this by surfacing the in-app notification feed and a tamper-evident event log for any node.

​
Export/Import tools (6)

ToolMutation?Purpose
thesis_export_subgraphNoExport a set of nodes and their edges as JSON
thesis_import_subgraphYesImport a previously exported JSON subgraph
thesis_export_summaryNoGenerate a Markdown summary from a node tree
thesis_export_summary_streamNoStream a Markdown summary as it is generated
thesis_export_summary_pdfNoGenerate a PDF summary from a node tree
thesis_export_summary_render_pdfNoRender a PDF from node IDs or pre-rendered Markdown

​
Subgraph export format

thesis_export_subgraph returns a self-contained JSON document that includes node metadata, content, edges, and artifact references. You can re-import this document into any Thesis workspace using thesis_import_subgraph.
​
node_ids
string[]
required
One or more root node IDs. The export includes these nodes and all of their descendants.
​
include_artifacts
boolean
default:"false"
When true, the export includes artifact metadata (but not file contents) for each node.

​
Example: export a subgraph

POST /mcp-server
Content-Type: application/json
Authorization: Bearer thk_your_api_key

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "thesis_export_subgraph",
    "arguments": {
      "node_ids": ["a1b2c3d4-0000-0000-0000-000000000001"],
      "include_artifacts": true
    }
  }
}
The exported JSON contains:
  • version, schema version for forward compatibility
  • exported_at. ISO 8601 timestamp of the export
  • nodes, array of node objects with all content fields, kind, lifecycle, and parent_ids
  • edges, explicit parent/child edge list for the subgraph
  • artifacts, artifact metadata when include_artifacts is true

​
PDF and Markdown summaries

thesis_export_summary and thesis_export_summary_pdf generate human-readable documents from a node tree. Use thesis_export_summary_stream when the document is long and you want to display output progressively rather than wait for the full response. thesis_export_summary_render_pdf accepts either a list of node IDs or a pre-rendered Markdown string, giving you control over the exact content that appears in the PDF. This is useful when you want to post-process or annotate the Markdown before rendering.
​
node_ids
string[]
required
Node IDs to include in the summary. The summary follows the tree structure rooted at these nodes.

​
Updates tools (4)

Thesis surfaces in-app notifications when significant events occur, new collaborator activity, completed Oracle jobs, or approval decisions. The Updates tools let agents read and manage this feed.
ToolMutation?Purpose
thesis_updates_listNoList current notifications in the feed
thesis_updates_hideYesHide a specific notification
thesis_updates_unhideYesUnhide a previously hidden notification
thesis_updates_hide_all_activeYesHide all currently active notifications at once
​
update_id
string
required
The notification ID, required by thesis_updates_hide and thesis_updates_unhide.

​
Audit tool (1)

The audit log records all significant events for a node in an append-only, tamper-evident sequence. Use it to reconstruct the full decision history for a node, who made changes, when, and what was modified.
ToolMutation?Purpose
thesis_list_auditNoList audit events for a specific node
​
node_id
string
required
The node whose audit trail you want to retrieve.
​
limit
number
default:"50"
Maximum number of audit events to return, in reverse-chronological order.
The audit log is read-only and cannot be modified or deleted through the MCP API. It records mutations made through both the MCP tools and the Thesis web application.