Skip to main content
Glama
S2thend

cursor-history-mcp

by S2thend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

cursor_history_migrate

Move or copy eligible Cursor Composer sessions between workspaces. Use dryRun to preview, and back up before moving to avoid data loss.

Instructions

Move or copy eligible Composer sessions between workspaces. Store-only, merged-source and ambiguous sessions are refused. Use dryRun to preview. Moving removes the original; back up first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoMigration mode: 'move' deletes original, 'copy' keeps originalmove
dryRunNoPreview without changing history (default: false).
workspaceNoSource workspace scope; use the same scope that produced the session indexes.
sessionIdsNoExact native UUIDs from list/search. Use instead of sessionIndexes for stable selection.
destinationYesAbsolute path to the destination workspace folder
sessionIndexesNoList of session indexes to migrate (1-based, as shown in list output)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.1
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "sessionIds"
+      ]
+    },
+    "required": [
+      "sessionIndexes"
+    ]
+  },
+  {
+    "not": {
+      "required": [
+        "sessionIndexes"
+      ]
+    },
+    "required": [
+      "sessionIds"
+    ]
+  }
+]
    • addedInput schema / properties / dryRun
      Added value: +{
+  "default": false,
+  "description": "Preview without changing history (default: false).",
+  "type": "boolean"
+}
    • addedInput schema / properties / sessionIds
      Added value: +{
+  "description": "Exact native UUIDs from list/search. Use instead of sessionIndexes for stable selection.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / workspace
      Added value: +{
+  "description": "Source workspace scope; use the same scope that produced the session indexes.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "sessionIndexes",
-  "destination"
-]New value: +[
+  "destination"
+]
  2. First observedv0.2.4

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral disclosure. It clearly warns that moving removes the original, recommends a backup, mentions that certain session types are refused, and points to dryRun for preview. This is strong disclosure, though it does not cover permission requirements or overwrite/conflict behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler. The core action is front-loaded, followed by eligibility constraints, a preview recommendation, and a safety warning. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with six parameters, a oneOf selection constraint, no annotations, and no output schema, the description covers the main workflow, eligibility, preview, and destructive consequences. It does not explicitly describe the return value or whether the destination workspace must already exist, but those are minor gaps given the rich schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents each parameter. The description adds little parameter-specific meaning beyond restating that dryRun is for preview and move deletes the original, which are also encoded in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Move or copy') on a specific resource ('eligible Composer sessions') with an explicit scope ('between workspaces'). It also distinguishes the tool by naming ineligible session types, making it easy to separate from backup/restore/export siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: when sessions need to move or copy between workspaces. It also tells the user to dryRun first and back up before moving, but it does not explicitly contrast this tool with sibling alternatives such as backup/export/restore or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools